Jacob Lifshay
Jacob Lifshay
> semantics impl > shift checking `if m < BITS { Some(n shift wrapping `n shift saturating `n result checking `if m < n.leading_zeros() { Some(n result wrapping `n.rotate_left(m.rem_euclid(BITS))` that's...
one alternative option is to do something like Java's jar files...scripts would be a zip file with a different file extension and a unix `#!` line prefixed
seems like `UniqueArc` would be a good alternative...it's not in nightly yet, but the `Rc` version is: [`UniqueRc`](https://doc.rust-lang.org/nightly/alloc/rc/struct.UniqueRc.html)
don't forget shifts by and conversions from/to `usize`/`isize`, additionally `fmt::LowerExp + fmt::UpperExp` should be on `Float`
I ran into the same issue, hopefully a fix can be merged soon
> In the example I gave, I used `Default + PartialEq` as the bound on the parameter, under the assumption that you could do something like `extra == Default::default()` to...
I know it was mentioned somewhere else, but one possible reason that `unsafe` would still be desired is that allows `unsafe` code to depend on `BTreeMap` being sorted, duplicate free,...
> ```rust > enum StringOrStr } > ``` that's already in the standard library as `Cow
> What I mean is, is `UnsafeCell::get_mut` the only difference in implementation between the two. maybe in the library but not in the compiler.
I think `bfloat16` or `bf16` are the only good options for that type, because they are the de-facto standardized names (ignoring the extra underlines C/C++ compilers like to add). I...