Skip to main content

Notes from 5/28 Dart Language design meeting

Posted by Bob Nystrom

Sorry for the long delay. This meeting was just skimming over a bunch of issues in the bug tracker, so forgive me if there isn't a lot of context here.

Import syntax

Kasper and Ivan did the original syntax design. If we want to iterate on that, we should get them in a room.

Catch syntax

Looks weird because it's more like a variable declaration than a parameter declaration. Gilad says we'll figure it out soon and should be a minor change.

Statics in interfaces

Kasper: People find default classes hard to follow. We could consider allowing simple redirect code for constructors in interfaces.

Instance field should be allowed in initializer expression when it is initialized via "this.foo" sugar.

Bug 3263. Gilad says: if the sugar doesn't do what you want, don't use the sugar.

Private names

Dart uses isolates for security, so we don't feel pressure to have JS-private-names-style security.

The default implementation of an interface must not over-specify generic paramaters

Bug 3279. We're OK with the current semantics.

Abstract or static method named the same as enclosing class

Bug 3284

Kasper: The VM is slightly broken with respect to reporting. We should clarify the spec.
Lars: It is very confusing.
Gilad: That's why shadowing is a warning.
Kasper: Should say that if it's the same name, it must be a constructor. If it has a return type or abstract, that's an error.

Function expression vs statements

Can we get rid of return types and/or names?

Bob: Idiomatic dart doesn't have return types or names for function expressions. The style guide may discourage it soon. [ed: it does now.]
Kasper: Getting rid of return type for function expression gets rid of the nasty infinite lookahead with generic return types.
Gilad: What about contexts where you can't distinguish between expr or stmt?
Kasper: If it has a return type or a name, it's a statement. Done. It must be in statement position.
Gilad: Let me try to come up with some rules for it to see if it hangs together.

Comments

Popular posts from this blog

Const, Static, Final, Oh my!

Posted by Seth Ladd

(This is an "oldie but a goodie" misc@dartlang.org post originally written by Bob Nystrom. It is being posted here as the explanations still ring true.)

Bob writes:


"static", "final", and "const" mean entirely distinct things in Dart:

"static" means a member is available on the class itself instead of on instances of the class. That's all it means, and it isn't used for anything else. static modifies *members*.

"final" means single-assignment: a final variable or field *must* have an initializer. Once assigned a value, a final variable's value cannot be changed. final modifies *variables*.

"const" has a meaning that's a bit more complex and subtle in Dart. const modifies *values*. You can use it when creating collections, like const [1, 2, 3], and when constructing objects (instead of new) like const Point(2, 3). Here, const means that the object's entire deep state can be determ…

The new AdWords UI uses Dart — we asked why

Google just announced a re-designed AdWords experience. In case you’re not familiar with AdWords: businesses use it to advertise on google.com and partner websites. Advertising makes up majority of Google’s revenue, so when Google decides to completely redo the customer-facing front end to it, it’s a big deal. The Dart team is proud to say that this new front end is built with Dart and Angular 2. Whenever you asked us whether Google is ‘even using Dart for anything,’ this is what we had in mind but couldn’t say aloud. Until now. We asked Joshy Joseph, the primary technical lead on the project, some questions. Joshy is focusing on things like infrastructure, application latency and development velocity, so he’s the right person to ask about Dart.Q: What exactly did we launch on Monday?It’s a complete redesign of the AdWords customer experience that is rolling out slowly as a test to a small initial set of advertisers. The most noticeable thing is probably the Material Design look and f…

Dart 1.12 Released, with Null-Aware Operators and more

Dart 1.12.0 is now released! It contains the new null-aware operators language feature, and enhancements to pub, Observatory, dartdoc, and much more.

Null-aware operators

The new null-aware operators help you reduce the amount of code required to work with references that are potentially null. This feature is a collection of syntactic sugar for traversing (potentially null) object calls, conditionally setting a variable, and evaluating two (potentially null) expressions.

Click or tap the red Run button below to see them in action.

??

  if null operator. `expr1 ?? expr2` evaluates to `expr1` if not `null`, otherwise `expr2`.


??=

  null-aware assignment. `v ??= expr` causes `v` to be assigned `expr` only if `v` is `null`.

x?.p

  null-aware access. `x?.p` evaluates to `x.p` if `x` is not `null`, otherwise evaluates to `null`.

x?.m()

  null-aware method invocation. `x?.m()` invokes `m` only if `x` is not `null`.

Learn more about Dart's null-aware operators in our Language Tour.

.packages fi…