Sébastien Doeraene
Sébastien Doeraene
A method that happens to be named `unapply` only takes on an *extractor* meaning in the context of pattern matching, which is a *use site*. There is no reason to...
What's the change of behavior, here? IIUC we're only turning an obscure error message into * either a clean error message for the `Nothing` case, or * the already-specced behavior...
Scala.js also suffers from this issue. So far I haven't found a good way to solve it. :(
Er, no? That would prevent serializing an object that contains a unit value. I don't understand why the compiler wants to internally pretend it's not serializable. But in practice, at...
This PR's communication is off. The *value added* by the first commit is that `tap` and `pipe` become more `inline`, guaranteeing that they have no overhead. That's what the commit...
The error message is misleading, indeed. But it is according to spec that the former is legal and not the latter. The former constitutes a "type member extractor".
> which should be written in backquotes They should not be written at all, in fact. ;)
> As a compiler, we should still try our best to generate efficient and non-redundent code possible. Not really. Our job is to generate code that the next compiler in...
This bound (ah ah!) to be break something. There are very real things we can do with type aliases that we cannot do with abstract type members of equal bounds....
Perhaps. There are definitely other things that require an actual type alias. Extending or instantiating an aliased class, for example. And that will remain through inlining.