Bob Nystrom

> Personally, I really dislike the # symbol for representing Symbols. Agreed. I would remove symbol literals from the language entirely if it were up to me. They don't carry...

> Also, merging is a process that produces a library from _something_, which is represented by the text of the main library and the augmentation libraries, but might also be...

> It is technically possible, that any time a package is published, that could affect the API of any other package that depends on it, if they are using particularly...

Another reason in favor of using metadata annotations for macro applications is that macros will often need metadata annotations applied to declarations anyway, to configure how the macro behaves. For...

It's just a proposal, so we don't need to officially "abandon" it since all proposals default to being in a "not going to be shipped" state unless they get accepted....

> I would have expected the matching to behave like a subtype check, so: > > 1. If the type being matched is a nullable type or a star type,...

> * It's called a "library augmentation", not an "augmentation library". SGTM. Jake's PR #3583 does this. > * It's imported using `augment import "...";` or `augment part "...";`, just...

> It's the difference between native and web semantics that really makes things tricky, and disallowing doubles avoids a lot of trouble. I mean, we have that problem with *all*...

I am 100% OK with not allowing you to augment mixin application classes. Mixin applications are, as far as I can tell, basically a useless feature as far as solving...

I agree with @Levi-Lesches that I don't think pattern matching should do this lifting *implicitly*. But I do think there's merit to, essentially, a "null-aware" pattern match operator of some...