Our great sponsors
-
WorkOS
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.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
The Rust book doesn't seem to mention it in section 3.2, although it does describe, eg. the syntax for integer literals of different bases. This might be an example of something that's omitted by accident simply because it was too obvious to the author; the 1e123 syntax is ubiquitous in modern programming and mathematics languages. Might be worth submitting an issue, however because the digital book is intended to be kept in sync with the deadtree version, it's not clear if or when the change would actually happen :/
But DDOSing is probably almost never an issue when you're doing no_std (or at least you know what you're doing), so not including an extremely useful thing in alloc only because some specific use cases would be less secure is pretty much the definition of throwing baby out with the bathwater. Because the randomness is factored into the RandomState parameter, there should be a way to have Hash* without randomness in alloc, and there's been desire to do just that at least since Rust 1.0, but unfortunately it seems the issue is stuck in limbo :/
std’s HashMap and HashSet are available as no_std library https://github.com/rust-lang/hashbrown, the std just imports those and wraps around them
Yes, they are declared as pub in main. See here I'm using pub mod with the modules I'm trying to use (environment and ast) and here I'm trying to import them in mod.rs as I said, but I'm getting out of ideas!
You can use cargo-make to make a custom cargo make lint command. This is what I use if I have commands that aren't supported or are too complicated to type over and over.
You might have to make your own syntax rule, I rate. Did you have a look at rust-enhanced?