matthieu-m

> To define helper attributes, put an attributes key in the macro_derive attribute, with a comma-separated list of identifiers for helper attributes: `#[macro_derive(attributes(helper))]`. The derive macro can process the `#[helper]`...

> I don't think that's a good idea. > For clap, namespacing by crate or derive name was insufficient and it now processes 4 different namespaces. I would note that...

> Overall, I think this RFC is in the right track, but I'd postpone it until we're past Rust 2024. Are you proposing delaying the _discussion_ or the _implementation_? My...

For the sake of completeness, I think it would be worth trying to evaluate user requirements. Off the top of my head: ### Library developer The developer of a library...

For the sake of completeness, I initiated two discussions on IRLO: - ~~[Pre-RFC: Allow where clauses on concrete types](https://internals.rust-lang.org/t/pre-rfc-allow-where-clauses-on-concrete-types/23544)~~ (Tracking issue #48214 for `features(trivial_bounds)`, a `for

I'd like to share a concrete usecase for this feature. In the [RFC: Introduce the Store API for great good](https://github.com/rust-lang/rfcs/pull/3446) the `Store` trait has been artificially split into `StoreDangling` which...

> This RFC cannot help with eventually making `Iterator` const, since adding `const` to a trait function would be a breaking change. Indeed, it cannot, but I do not see...