Any "surprises" in Rust to be aware of?

• unsafe-code-guidelines

  74 639 6.9

  Forum for discussion about what unsafe code can and can't do

  

It seems to me like a number of programmers think that they can just drop into an unsafe block to bypass compiler errors, or follow the intuition they have from writing C or C++ and that is wrong. The prototype aliasing model is documented here, but honestly, just run Miri.

• aHash

  11 928 7.2 Rust

  aHash is a non-cryptographic hashing algorithm that uses the AES hardware instruction

aHash has a very good comparison doc: https://github.com/tkaitchuck/aHash/blob/master/compare/readme.md (Personally, I use it more to compare non-aHash hashes than to aHash; aHash has no reason to be biased between other hashes, though it does have reason to be biased for itself. I trust their analysis to not be biased, but it's always better to be more sure.)

• WorkOS

  workos.com sponsored

  The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

  

• rfcs

  666 5,700 9.8 Markdown

  RFCs for changes to Rust

  

This is a big confusing mess. For a long time we tried to have some kind of “5-second rule” thing where if you converted the reference to a raw pointer “fast enough” then it’s OK but that was pretty clearly untenable for a formal model. So folks came up with a proper RFC for raw addresses and for a long time we’ve had a hacky addr_of macro that lets you do this:

Suggest a related project