News for hackers. Stuff that matters.

A comment on Why Hashbrown Does a Double Lookup. Parent comment

Re:Why Hashbrown Does a Double Lookup by half-kh-hacker on Wednesday March 20, 2019 @05:10PM (#19446969)
I'm not a Rust expert, but I think ownership and borrowing go away after compile-time.
[ Parent | on HN ]
Re:Why Hashbrown Does a Double Lookup by aswanson on Wednesday March 20, 2019 @09:59PM (#19448696)
Of course, but what pre-compile architectural decisions could be made to accommodate such a higher level construct?
[ Parent | on HN ]
Re:Why Hashbrown Does a Double Lookup by incog-neato on Thursday March 21, 2019 @06:45PM (#19458103)
The point of the borrow checker is that it's run at compile time rather than runtime. Putting something similar into the architecture necessarily implies a runtime check, which is similar to the idea of a smart pointer, which exists in Rust as well as other languages.
[ Parent | on HN ]
Re:Why Hashbrown Does a Double Lookup by steveklabnik on Wednesday March 20, 2019 @09:00PM (#19448453)
That’s correct.
[ Parent | on HN ]