Lasse R.H. Nielsen

Maybe we can detect variance and make it a compile-time error. I don't think we can avoid unsoundness if we allow it. We may be able to detect it at...

I don't think inlining/short-circuiting redirecting constructors will work. I think it may make sense for the initial `Something.name()` invocation, but those can be covariant anyway. For a constructor called as...

It's an interesting idea, which I have already been looking at in other contexts (statements evaluating to a value). There are some syntactic issues which needs fixing, though. It's not...

> One of the most inconvenient parts of the switch expression syntax is its inability to use statements. FTFY. It's a general problem, I don't think a solution should be...

Tokenization as `if ([]= = [])` is what I expect too. Normally I'd check how the formatter would lay it out, but that only works if the code parses. Checking...

The only place the `[]=` token occurs in the language grammar is the `` production, which only occurs in a declaration after `operator` and in a symbol literal after `#`....

Keeping this open as a request to make `[]=` not work as a single token in places where that token cannot occur. (Or at least give better error messages when...

> `const factory D(args1) => e;` where `e` is potentially constant - I want this. (I always did, but I still do: #3356). > For each invocation of _k_ as...

(Summary derived at after having written the below: I think this can work. I just want more, but I think it'll be compatible.) I like the idea, and I'm pretty...

> It is again crucial that `TState` is computed (based on static information for a poor man's version, or on the run-time value of `TBloc` for a more powerful mechanism)....