Ryan Levick
Ryan Levick
Hi 👋. I'd like for the config parser to be fully idempotent meaning when I parse a config and immediately write it out again, I'd expect to get the same...
Should deriving `InvariantFree` require that a structs fields are the same pub level as the struct?
Since `InvariantFree` types are meant to represent types without invariants, it should reason that all the fields of the type should be accessible. Should we require that a structs fields...
Closes #6
Having some sort of trait for talking about a type's alignment at the type level will be useful not only for safe transmute but for other things as well. This...
The layout of the cargo-component Cargo.toml configuration needs to be documented preferably with the most common configuration items called out in the README.
I have a workspace that has some components within it so I am using `cargo component check --workspace` to check that all of the workspace members are working. However, one...
We want to make sure we have documented who the Council representatives are. This might be as simple as linking to the team repo and/or [governance page](https://www.rust-lang.org/governance/teams/leadership-council). We also want...
Many policies state that decisions are made by consensus, but the term "consensus" might not be precise enough. Consensus may mean "active consensus" whereby all members actively agree with each...
As noted [here](https://rust-lang.zulipchat.com/#narrow/stream/392734-council/topic/Documenting.20Meeting.20Process/near/369008621), documentation can easily become stale over time. This is particularly true for things that are explicitly temporary. Ideally we would have tooling that would automatically inform us...