Lasse R.H. Nielsen

I don't want to institutionalize the current static analysis. (In some places I want to change it!) I do want a consistent (as well as possible within constraints) and predictable...

I think we have features sufficient to make this work already. Yes, creating a new listener every time you ask for one is probably a problem. Not an insurmountable one,...

The problem with using the return address is that Dart code might live on the heap, and it can be moved by garbage collection. That's not a complete blocker for...

This is in some ways similar to #43 (pipe-operator). You take the result of an expression and use it as the first argument to a following function, `e1 -> function()`....

The question here is what the goal of the operation is. If it is to make implicit `this`-calls possible, as a way to reduce the syntactic overhead of introducing a...

Indeed my rule for whether a specialized construct is worth it when a general construct already enables the functionality is that: * The specialized functionality is signficantly "better" (e.g., more...

It's not new to want some null awareness with operators. Not sure this precise version has been suggested as its own issue before. (I cannot find things using GitHub search...

Agree. Types are used during compilation, fx during type inference, and exists whether code is executed or not. Values, including instances of `Type` from type literals, only exists when code...

Thinking more about inferring deferred types. We can't assume that every type that is mentioned in the deferred import's API is itself deferred. The only things we know are deferred...

OK, having thought more about it, and Erik saying that we can decide whether a type is deferred or not in general, not just through a prefix, how about: *...