Skip to main content

Dart language spec v0.07 now available

Posted by Kathy Walrath

Version 0.07 of the Dart language spec is now available.

Changes include:
  • 5: Top level variable initializers must be constant. 
  • 7: Added abstract modifier to grammar. 
  • 7, 7.6, 7.7, 10.13.3,10.28: Superclass static members are not in scope in subclasses, and do not conflict with subclass members. 
  • 7.1.2: []= must return void. Operator call added to support function emulation. Removed operator >>>. Made explicit restriction on methods named call or negate. 
  • 10.1: Added !e as constant expression. Clarified what happens if evaluation of a constant fails. 
  • 10.7: Map keys need not be constants. However, they are always string literals. 
  • 10.9: State restrictions on use of this. 
  • 10.10, 10.10.1: Rules for bounds checking of constructor arguments when calling default constructors for interfaces refined. 
  • 10.14.1: Revised semantics to account for function emulation. 
  • 10.14.2: Revised semantics to account for function emulation. 
  • 10.14.3: Factory constructors cannot contain super invocations. Revised semantics to account for function emulation. 
  • 10.16: Specified assignment involving []= operator. 
  • 10.16.1: Removed operator >>>. 
  • 10.22: Removed operator >>>. 
  • 10.26: Postfix -- operator specified. Behavior of postfix operations on subscripted expressions specified. 
  • 10.28: Added built-in identifier call. Banned use of built-in identifiers as types made other uses warnings. 
  • 10.29: Moved specification of test that type arguments match generic type to 13.2. 
  • 11.8: Corrected evaluation of case clauses so that case expression is the receiver of ==. Revised specification to correctly deal with blank statements in case clauses. 
  • 11.15: Fixed bug in assert specification that could lead to puzzlers. 
  • 13.2: Consolidated definition of malformed types. 
  • 13.5: Revised semantics to account for function emulation.

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…

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…

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…