Replying to
@DocBohn@techhub.social @az@scorpinc.social it's a bad idea to open windows in space...
Remote
In a recent screenshot from @blyxyas@tech.lgbt I saw that a rustc lint took a lot of allocations. So I found out why and removed those. The PR was finally merged into nightly.
Replying to
@Mara@hachyderm.io I'm sure they've already solved it in those modern C++ code bases that I keep hearing about (but lamentably haven't had a chance to see yet).
Replying to
@Mara@hachyderm.io damn! And I've been calling unsafe core::arch functions without a lincense for years now. Hope the Rust police won't cite me...
Replying to
@Mara one more point where you go the extra mile to accommodate us. Other conf organizers should borrow those steps (or if they are Copy, just take them).
Replying to
@Mara last year you made the most of that with an epic trailer. Looking forward to this year's edition.
Replying to
@ghostwriter@phpc.social is it though? I'm seeing far more small abstractions than borrow checker appeasing misuse.
Replying to
@david_chisnall there are some experimental electrified roads in Germany (with cables overhead), but just a kilometer. I happen to regularly drive on one near Frankfurt. As far as I know, the whole thing is already switched off though.
Replying to
@jakub_neruda@techhub.social @Mara@hachyderm.io That makes me worry about the memory errors you didn't encounter.
Replying to
@jakub_neruda@techhub.social @Mara@hachyderm.io so what does "rarely an issue" entail? What tools do you run? What practices do you follow to avoid things like e.g. iterator invalidation?
Replying to
@lholten@hachyderm.io missing an "it depends" option for the senior devs here...
Kidding aside, I would make it dependent on whether the user should care about the trait or the type. E.g. if the trait is just used internally, I'd put its impls together with the definition, unless the file would get too big.
Replying to
@428@mas.to if you built in debug mode, you may have happened upon a stack overflow because the compiler didn't elide an on-stack initialization that was later to be moved to the heap. Otherwise there may be some unsafe code that fails to uphold some invariant.
Can you cargo miri run? It will be very slow, but might find UB on your active code path.
Replying to
@grumpygamer@mastodon.gamedev.place that's a pretty unkind thing to say...
...against typical idiots.
Replying to on mastodon.social
@bruces@mastodon.social I hate to be pedantic but wouldn't it be 1/355.0249975 light-years?
Replying to
@rustinparis@mastodon.social I have suggested a talk. If that one doesn't fit, I could do other talks. How would I go at adding more suggestions?
Replying to
@jakub_neruda@techhub.social @Mara@hachyderm.io I agree that logic bugs are a problem even in Rust – although in my experience they are easy to find. i use assertions liberally, so if the data flow fails to fit my mental model, I will get a panic with useful information.
Conversely, memory bugs may be masked by the allocator (depending on the system) or only ever become visible in uncommon circumstances. Running ASAN is great practice, but even that will only check all the code paths that have been taken during the test run with the given data. Tools can usually only detect the presence of bugs, not their absence.