Github RFC: `cargo`-`miri` integration by mark-i-m · Pull Request #3099 · rust-l...
source link: https://github.com/rust-lang/rfcs/pull/3099
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
Conversation
I've been meaning to write this RFC for years now, but the opportunities just keep passing me up... until now 
Feels like you're a day early.
@Lokathor The date is correct in Japan.
[unresolved-questions]: #unresolved-questions
- Are corgis really the best dog to name this tool after? The name at least sounds like `cargo` a bit...
- What about all the cat-lovers in the rust community?
Kixiron 5 days ago
Member
Who needs 'em? This is a non-issue, please remove it from the unresolved questions as it's quite self-evident
petrochenkov 4 days ago
Contributor
What about all the cat-lovers in the rust community?
Miri is a cat in the first place, so their needs are already covered.
I suppose technically so, but midnight-30 is still pretty early
Yeah, I wrestled with that too... problem is if I posted it when I wake up on April 1, it will already be over for most of the world...
I hate living on an ellipsoid :( Maybe somebody should post an RFC to change that....
corgi fetch -- ellipsoid
Thank you for this RFC, i always feel that people use too many dependencies and cargo should make build times exponentially worse the more dependencies you use, up until the deno folks have to figure out how to run cargo for 3 weeks with their ~400 dependencies. Have you considered running everything on top of valgrind? then for every byte leaked you add 1 second to the build times just to discourage leaking? It would also make miri even slower, thereby increasing the effectiveness of this RFC.
then for every byte leaked you add 1 second to the build times just to discourage leaking?
Actually, this seems like a good approach to bugs in general... for each bug in the program, add 1 second to the run time.
@mark-i-m But aren't bugs... like bugs and u can't actually easily detect them?
Copy link
Ekleog commented 4 days ago
I mean I've got a butterfly net so that allows me to detect some of the bugs
@Ekleog How would we download the butterfly net to catch the bugs for everyone
@mark-i-m I feel emails are too basic for such a task.
We should create a server exactly at the center of the earth and have it digitally send butterfly nets through websocket connections that are opened by cargo whenever a command is run and never closes until the computer shuts down. That way everyone can have butterfly nets and we can also punish people for using cargo.
Why would we want to punish people for using cargo?
Reject Rust, return to Assembly.
Why would we want to punish people for using cargo?
Reject Rust, return to Assembly.
Hmm... assembly such a pleasure to work with, though, especially compared to rust... is it really a punishment?
@mark-i-m But aren't bugs... like bugs and u can't actually easily detect them?
But bugs add weight to the program, so obviously they will make it slower.
As a lead of the @rust-lang/miri team, I fully approve of this proposal. :)
> - Why is this design the best in the space of possible designs?
Seems obvious, right? `miri`.
oli-obk 4 days ago
Contributor
Yes, this is the best reason, and anyone who argues otherwise should obviously be writing their build scripts in assembler
As a lead of the @rust-lang/miri team, I fully approve of this proposal. :)
it
So can we get an fcp merge?
@mark-i-m But aren't bugs... like bugs and u can't actually easily detect them?
But bugs add weight to the program, so obviously they will make it slower.
So let's basically detect everything as a bug because everything is relatively slow but then once we make something slow that is a bug making us make it even slower basically creating a never ending program. Wonderful.
maybe there could also be a feature where if compilation takes more than 5s, then it switches to bitcoin mining for 10min giving you time to find bugs by reading through your source code again! obviously bitcoin mining is chosen since your basically guaranteed to have a hashrate only sufficient to make a few cents per day worldwide (due to ASICs being waay better than cpus at sha256). the resulting bitcoin can be used once a year (each april 1st) to fund cat food treats for miri!
I think it is time to close this. :) Thanks all!
No one assigned
None yet
No milestone
Successfully merging this pull request may close these issues.
None yet
Recommend
About Joyk
Aggregate valuable and interesting links.
Joyk means Joy of geeK