Jacob Lifshay

> Four, we had a good discussion about whether to go with `.#tag` or `.tag`. one big problem with the `.#tag` syntax is that it isn't usable in the very...

though, just `.tag` by itself may also conflict with a reasonable extension of enum [pattern types](https://github.com/rust-lang/rust/issues/123646), where you can directly access fields of single-variant pattern types without needing to `match`,...

in unresolved questions, can you add the problem that some features imply other features (e.g. `avx2` implies `avx`) and we should try to make updates synchronized so we don't see...

> The implementation of feature detection by `std` sounds separate from if `core`-only code can call upon feature detection and expect other linked code to provide it. If this is...

> @programmerjake yes that was my intention. > > My point is that this RFC is extending an existing and stable part of `std` to also work in `core`, and...

> I wonder if, like with `NonZero`, another way here would be to have `u` as something that can be written, with support for all the methods on that. like...

> Biased as the author of [rust-lang/rfcs#2581](https://github.com/rust-lang/rfcs/pull/2581), but I also would be largely in favour of having generic `uint` and `int` types (with `usize` and `isize` being separate as they...

> > agreed, though `f80` is also kinda weird since it has an explicit mantissa integer bit instead of an implicit bit like all other IEEE 754 types; still waay...

maybe look at https://wiki.libsdl.org/SDL3/SDL_Folder and https://wiki.libsdl.org/SDL3/SDL_GetUserFolder for inspiration

related, on Linux at least, common programs (e.g. `sshd`) are known to write over their `argv` strings since that's how they change what name they show up as in the...