Niko Matsakis

I think this is related to the [context/capabilities proposal](https://tmandry.gitlab.io/blog/posts/2021-12-21-context-capabilities/) that @tmandry, @yoshuawuyts, and myself have been looking into. I'm definitely interested in the idea of custom contexts of some kind,...

It is definitely more general than what is being asked for here, no doubt about that. But it has the advantage of being statically analyzed and verifiable. I'm concerned because...

I'm nominating this for @rust-lang/lang attention -- this is a principle that we have frequently enunciated internally, so I encouraged @tmandry to make an RFC for it. We don't necessarily...

We discussed this in the @rust-lang/lang meeting today -- we were thinking, @tmandry, that it would be better to make the `#[refine]` attribute mandatory for the refined signature to be...

@rfcbot fcp merge I think we've got consensus on most of this here -- the main question is whether, in the next edition, `#[refine]` ought to be required in order...

@rfcbot concern unresolved-question-for-next-edition Let's add an official "unresovled question" about the behavior in the next edition. I think the options to choose between are: * no edition dependent behavior: `#[refine]`...

@rfcbot fcp merge I think we've got consensus on most of this here -- the main question is whether, in the next edition, `#[refine]` ought to be required in order...

@rfcbot concern unresolved-question-for-next-edition Let's add an official "unresovled question" about the behavior in the next edition. I think the options to choose between are: * no edition dependent behavior: `#[refine]`...

(those commands were posted earlier, but since there was no T-lang label, rfcbot ignored me)

@rfcbot resolve unresolved-question-for-next-edition