Jarred Allen

@brother That's a workaround for this issue, but I feel like that shouldn't be necessary for the reasons I outlined in my initial post.

An extra function related to this that I've often found myself wishing existed (name unimportant and can be changed): ```rust impl [u8; N] { pub fn new_freeze() -> Self {...

I feel like providing explicit types for values should be assumed to be the default, and use of the `_` placeholder in types looks better to me: ```rust // I...

I added a `:where_clause`, as per multiple requests. They were excluded initially because I forgot that they existed, not for any real reason.

> I like the general idea of this RFC, but I don't like that a macro accepting `$( $p:generic_param $( : $b:generic_bound )? ),*` can accept illegal syntax (like a...

^ I am also interested in this.

For the solution, could we instead (or in addition? idk which) make a `--package` argument that lets you select one or more packages from a workspace to use to root...

> There are two fundamental problems here > > * Changing `cargo metadata`s behavior in a backwards compatible way It would be entirely backwards-compatible to add a new argument (`cargo...

> > ... > > By adding a `--package` flag, `cargo metadata` is starting to look like the other commands and people will be confused if it doesn't behave like...

I think so. The project was set up with the default [cargo-pio](https://github.com/ivmarkov/embuild/tree/HEAD/cargo-pio) for the SparkFun RED-V Thing Plus, because I'm trying to build targeting that chip, so it includes the...