Boxy
Relatedly consider the following two code examples: ```rust else if let Node::TraitItem(&TraitItem { kind: TraitItemKind::Fn(..), }) | Node::ForeignItem(&ForeignItem { kind: ForeignItemKind::Fn(..), }) = tcx.hir_node() { x } ``` and ```rust...
Add `covering set` impl for generic version of trait when all values of a const are covered by impls
> I've currently only implemented it for bools (and I'm not sure if this implementation is sufficiently functional), but I'm not sure how generic it should be here if we...
Add `covering set` impl for generic version of trait when all values of a const are covered by impls
all const generic types should have that property or else we've made a bit of a mess of the structuraleq thing i think haha
r? @Mark-Simulacrum
@Jules-Bertholet extending the type system with the ability to require subtyping is a significantly more involved undertaking than a simple `async Ty` desugaring. It should not be done as a...
@traviscross is this blocked on you ("with a lang team vibeck")? I'm not clear on what the next steps are and would really like to get this merged in some...
Personally `_::new()` and `_::Variant` "look wrong" to me although i cant tell why, I would expect `::new()` and `::Variant` to be the syntax, no suggestion on `_ { ... }`...
this is now in the stable PR. if the commits could be squashed then this can be r+'d
@Ddystopia inline consts desugar to an item that uses all in scope generic parameters, you should remove the `const` block there as it does not accomplish anything, if you need...