Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

The kind of reasoning we do is "if thread A writes to this location, then next time thread B writes to this location, it will have to take ownership of the cache line, which will take N cycles, so let's not do that". I don't think that kind of performance reasoning maps on to anything in Rust.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: