Skip to main content

### New site for Dart news and articles

September 10, 2019
For the latest Dart news, visit our new blog at https://medium.com/dartlang .

### Notes from January 7 language meeting

January 11, 2013
Dart engineer Bob Nystrom has posted the notes from the January 7th language design meeting. He writes:
Here's my notes from this week's meeting:
call() versus operator()
Gilad brought up the perennial discussion of how classes that emulate functions should define that operation: as a method named call() or using an operator syntax.
Lars: What are problems with making it an operator?
Gilad: At this point I think we could. It's an incompatible change, but not a big deal.
Configuration-specific code
Gilad has a rough proposal he's working on for this.
Method cascade grammar
[Bob: I think the Dart implementations and spec are out of sync regarding how they handle precedence of method cascades in particular with respect to the ternary operator.]
Gilad: The grammar for cascades makes sense from perspective of someone looking at the grammar, but not as much for someone trying to program using them.
Kasper: There are a couple of corners of the grammar that are confusing and there have been bugs filed. Maybe we should take a look at moving some things around.
Lazy loading libraries
Lars: Something to move up on the list is lazy loading. Aarhus has started working on this.
Kasper: Should be able to compile into multiple specific files that are loaded somehow on demand and can be stitched together.
Gilad: This and configuration-specific code are somehow related.
Cheers!
As always, we invite you to join our Dart mailing list , ask questions on Stack Overflow , or file feature requests on dartbug.com .