3 ms·
Well i didn't mean only defer, context managers also count as a 'making explicit'. My point is that requiring compile time proofs is likely too far to reach th
by mjburgess 4y ago
Well i didn't mean only defer, context managers also count as a 'making explicit'.
My point is that requiring compile time proofs is likely too far to reach the practical goal.
Indeed, it seems most Rust
code today agrees: widely turning off the borrow checking with copies and the like.
- jamincan 4y ago> Indeed, it seems most Rust code today agrees: widely turning off the borrow checking with copies and the like. I here this and that `unsafe` is widely used in Rust code bases repeated a lot, but is there any actual data backing this?
- mjburgess 4y agoThere are three "dialects" of rust: borrow-checked, unsafe, and copy-everything. The existence of these three "dialects" goes to my point that the borrow checker isnt The Ideal solution to the problem of high-perf. safe static computing.
- anonymoushn 4y agoSome of this data may be difficult to collect, because some project leads evaluate Rust, discover that the entire ecosystem is built on top of libraries that endlessly thrash a global allocator with synchronization primitives in it, and move on.