Skip to main content

Dart Language progress update

Posted by Gilad Bracha


The Dart language team gathered to discuss some of the open issues with the language.


Language Bugs: Will review language bugs and either fix, mark as deferred to future release (meaning no decision but distinctly possible in the future) or close. 30 bugs already processed last week.

Cascades: The new dart2js compiler has implemented the spec. We will review to see if spec needs minor adjustments in light of implementation experience. We don’t expect any significant changes.

Defaults in interfaces:  We expect to support these. Intended semantics are to give a warning if violated by implementor. However, if no default is given in the interface we will not interpret that as a default of null.  People can override in the default code if they want to, and may have reason to.  In any case we have no way force them to do otherwise. We will pin down draft specification.

Generics reification: We discussed whether to back off of that. The decision is to retain reification unless major problems arise in dart2js. We do not anticipate such problems, but once dart2js implements the semantics we can quantify any costs.

Multiple initialization points for finals:  Tendency is to keep current spec and fix implementation, but we do need to see what impact it has on code base. Ongoing discussion.

Repeated keys in map literals: We noted that we could disallow this if the keys are strings constants, but since we are hoping to generalize that, it might not make any sense.

Switch statement: Decision is to restrict switch to operate on compile time constants of uniform type - either int or String. We could extend this to enums if we ever add them. The motivation is that switch is only useful as a highly optimized jump table, and so we should focus on that; otherwise use if-else, it’s clearer. We will adjust spec accordingly.

Comments

  1. I run on the homepage the following programming
    main() {
    int iInt;
    num iNum;
    double iDoub;
    iDoub=1.5;
    iNum=iDoub;
    iInt=iNum;
    print('iDoub = ' + iDoub + ', iNum = ' + iNum + ', iInt = ' + iInt);
    }

    The result for iInt is 1.5. This is in my view completly sick.
    As an old hacker its generally funy to watch. Once upon a time there were no type types at all. E.g. in APL or at least a very loose type system. This was identified as a constant source of nasty bugs. So strict typed languages were invented. Now it turns back to the old typeless times. Probably the current generation of programmers has not experience why type-safty was invented. They just see the disadvantages.

    ReplyDelete

Post a Comment

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…