Josh Stone
Josh Stone
The regular `Entry` API doesn't help avoid that clone, because it always takes the key by value. You would need something more like `HashMap::raw_entry_mut` (rust-lang/rust#56167) or `BTreeMap` cursors (rust-lang/rust#107540).
@rfcbot reviewed > This also affects the library users, I guess we have to release this as 0.3. Strictly, yes, but I think we can exercise leeway here -- it...
Can we detect the difference in the build script's `is_musl_time64_abi`?
`struct timespec` as a whole should still only have 4-byte alignment on 32-bit though, despite padding that makes it look like 8-byte alignment. Plus, on big-endian that padding comes *between*...
> * Require rust >= 1.56 so we can use `rust-version` You don't *need* 1.56 for `rust-version` -- it's ignored on earlier versions, but still serves as documentation. ``` warning:...
> 1. "I did `sudo apt-get install rustc cargo`, cloned your repository and then tried to run `cargo build`." In effect, they are trying to port workflows that they expect...
I don't have hard customer data to offer here, but I think there's also a chicken-and-egg problem, that Rust won't even be a viable option for those customers at all...
Fair enough. :)
> Add an outsider, it's pretty intuitive to me that any "saturating" operation applies to the result, not the operands. Do you also think that about checked/overflowing/wrapping shifts? Because all...
I doubt it will ever be exposed, but for a given version you can inspect the source. The immediate size is just `std::mem::size_of::()`, and the heap size comes from the...