Lasse R.H. Nielsen

I'm not worried about existing `super._`s, I'm worried about future ones, written by people who expect it to work, because there is no obvious reason for it not to work....

> "`_` is a wildcard" My problem with that problem statement is that it doesn't tell me anything about how it actually works. I have some (wild) associations to "wildcard",...

It's not impossible. We currently make `enum` classes extend `Enum` (implemented as extending `_Enum` which extends `Enum`) because it gives us a shared implementation of `index` and `toString`, and more...

Using a macro, or just generating the fields directly on the `enum` class has two problems: 1. Not being able to access the private `_name` field. 2. Duplicating code that...

This is a variant of the "implicit cast from representation type to extension type" idea. It's shorter than expanding to `=> Superclass(args);` and allows being a const factory constructor. There...

If you consider the superclass of C to have all the members that it declares or inherits, then there is no need to look further into the superclass chain (well,...

I'm not sure it makes sense to not inherit inaccessible members - depending on what "inherit" means in this context. If class `C` in library `L1` has methods `foo` and...

So you are saying that "inherit" in this case is only talking about the interface, because the implementation isn't "inherited" at all, but rather "looked up" in the superclass chain?...

I think this is one of the consequences of the semantics not decomposing expressions along grammar productions. The grammar here is: ``` cascadeSection: ‘..’ (cascadeSelector arguments*) (assignableSelector arguments*)* (assignmentOperator expressionWithoutCascade)?...

The `X & S` type promotion result is only used when `X` is a type variable, and `S` is a subtype of the bound of `X`, and it arises from...