Bob Nystrom
Bob Nystrom
Based on an internal discussion, I did a quick scrape of of a corpus of pub packages to see how often this feature might be useful. I only considered the...
In general, yes, it's nice if we can use static analysis to completely eliminate a class of runtime failures. At the same time, static analysis does have a cost: 1....
My inclination is to disallow all kinds of generative constructors in extensions. You get factory and const factory, but that's it. I understand that eliminates some edge use cases around...
I analyzed a big corpus of pub code to see how many existing `?:` expressions have `null` in one of the branches. I tried to exclude generated files from the...
> The ones that have null in the else branch can immediately be abbreviated simply by deleting : and null, and the ones that have it in the "then" branch...
Oops, you're almost right. Fixed, thanks!
Oh, good point. Added one to this in-progress PR: https://github.com/dart-lang/language/pull/4468
> Do we consider to just introduce keyword `private` to handle this properly? I think it would be really strange to use `private` as a modifier for privacy in one...
> I mean everywhere. There is no way to describe that feature with "just" then. It would be an absolute mountain of work and it's entirely likely that the result...
> isn’t that something that could be automated with a migration tool? Or are there edge cases? It's *very* common for a class to have a private field named `_foo`...