radiish

we could allow associated constant type names with a fixed length array as storage which would panic on overflow instead of using `const_format` e.g. ```rust trait TypeName { const NAME:...

@CertainLach’s implementation would be a breaking change since [this basic usage](https://play.rust-lang.org/?version=nightly&mode=debug&edition=2021&gist=aa3eef5b14ff9a743116981cbb027584) does not compile

if/when you add keybindings to the site, this wouldn’t be a problem. ctrl just wouldn’t be a valid sprint key

i don't think `Component: Sized` should be controversial. IIRC, all bounds are `T: Component (+ Sized)` since that's a pretty important invariant for storage, and `dyn Component` is both already...

i think better names than `compose`: 1. `reduce` - matches `Iterator::reduce` - which takes in `n` inputs, returns `0..=1` outputs 2. `fold` - matches `Iterator::fold` - which always results in...

i wonder if we could implement a `Spherical`/`Cylindrical` wrapper (that works over all vectors), like [`Wrapping`](https://doc.rust-lang.org/stable/std/num/struct.Wrapping.html) and [`Saturating`](https://doc.rust-lang.org/stable/std/num/struct.Saturating.html).

no blockers here as i see. i think a PR reflecting most `std` types (especially with `reflect_value`) would be unambiguously approved - it's just churn. unfortunately considering there are *a...

> It should be possible, though I wonder whether there is a more general way to do this that covers any `Trait` that has a blanket implementation `impl Trait for...

what about `#[reflect(not(FromReflect))]` (like cfg attribute) or (my favourite) `#[reflect(!FromReflect)]` (like negative impls)

note that the `.properties` spec officially supports key escapes like the following: ```properties component.minecraft\:custom_name=Example ``` also, we should probably be using `components` instead of `component` to fit with the [NBT-ified...