← Back to context Comment by zombot 8 days ago Borrow-checking the dereference of a stale pointer won't be worth much, though. 3 comments zombot Reply josephg 7 days ago Sure; but I bet raw pointers are used very infrequently in the new codebase. The code was ported from zig to rust. I bet a lot of pointers became rust references in the process. zombot 7 days ago The point of compiler-based checking would be that you know for sure. If you have to bet, all bets are off. gcr 7 days ago That’s my whole point! It’s ported to unsafe rust, not default rust.
josephg 7 days ago Sure; but I bet raw pointers are used very infrequently in the new codebase. The code was ported from zig to rust. I bet a lot of pointers became rust references in the process. zombot 7 days ago The point of compiler-based checking would be that you know for sure. If you have to bet, all bets are off. gcr 7 days ago That’s my whole point! It’s ported to unsafe rust, not default rust.
zombot 7 days ago The point of compiler-based checking would be that you know for sure. If you have to bet, all bets are off.
Sure; but I bet raw pointers are used very infrequently in the new codebase. The code was ported from zig to rust. I bet a lot of pointers became rust references in the process.
The point of compiler-based checking would be that you know for sure. If you have to bet, all bets are off.
That’s my whole point! It’s ported to unsafe rust, not default rust.