Max “Goldstein” Siling

There needs to be some way to specify declension for this to work with some languages, e.g. it’s «13 ноября», not «13 ноябрь». TeX’s datetime2 does this by redefining date...

> that does not support new hardware Which new hardware are you talking about?

> Graphics for one Which, exactly? Could you name some models? Wayland has a lot of issues with all of the NVIDIA GPUs, so most GPUs on the market. You...

You still did not name any specific hardware, but okay, sure.

Slightly changing syntax of footnotes from: ``` Text[^footnote] [footnote]: Text ``` to ``` Text[^footnote] [^footnote]: Text ``` would allow to emit back-links inplace (if each footnote has only one associated...

There could be use in defining extern types with known alignment, like so: ```rust extern { #[repr(align = 8)] type Foo; } ``` This type can be the last field...

@WaffleLapkin Sure, it’s also `Aligned`. `MetaAligned` still seems to me like a more natural restriction for a tail field, although I’m not sure `MetaAligned + !Aligned` types are even achievable...

usize is guaranteed to be the same size as a data pointer, so seemingly if cast to a data pointer would truncate, cast to usize would too. Does Rust support...

Either way, if cast to `*const ()` is a problem, a cast to usize also is (because they’re guaranteed to be the same size). A cast to a wider type...

Side note: having something like `sptr::OpaqueFnPtr` in the standard library would solve the problem, because its `.addr()` could return an appropriately-sized integer on these architectures, causing a compilation error instead...