Omar Kamel

I'm not too hungry up on any specific implementation Rust has features, which only includes code if you specifically enable the feature on the package, which can be easily documented....

Just so I can contribute to the conversation, what exactly is modular compilation?

In that case, one possible option is to have the "features" compile into their own, independent mini-kernels that can be included or not In a lot of cases, the core...

> Yes, if we use "features", with separate libraries that you import to get support for each of the packages you use, then I see no major issues. The original...

Just a note on naming: this could be called "includes", which basically just has a string:package map, essentially. Otherwise, we could use "features" with the same, and reuse it for...

One option is: If we decide that features are just the exporting of a completely separate package (which may have extensions or which may add new subclasses) Then it would...

as far as I can tell, "final class" is the only ambiguity, right? Could we only allow using the word `class` as non-global variables? alternatively, we just check if its...

If this doesn't get done, I'd be willing to make my own PR, but I wont start unless I'm asked to. I'm the kind of person to make it super...

I'd argue that that particular example is better served with a collection extension: ```dart extension IterableSum on Iterable { int sum() => fold(0, (a, b) => a + b); }...

That said, i think I'd rather get a tangential-yet-similar feature of receiving any set of parameters in the shape of a record to be passed into the "actual" function, wrapper...