Is erased looking like it's ever going to stop being experimental?

I have normal implicits that derive stuff based on types as usual, this is all pretty “singleton type” based in general. The computed givens/implicits carry both value and type information, but usage wise, sometimes I want the value and so I use a typical using clause, other times I don’t need the values and just the computed types, so I put them in erased position.

It’s been a useful feature so far but I guess I could just duplicate the machinery to have it all inline def based and a non inline def version? the user (in reality just me) would have to know which givens to import and when, kinda annoying. I could also just do all inline defs but that’d be a nasty code explosion in general and goes against JITs too.

Now that capabilities are making their way into the standard library and are (or at least, seem to be) much more stable, is there a more tangible plan on hardening erasedand ideally see it graduate out of experimental?

3 Likes