commit | b71bd25a974fa3e7e5bcc156f7d746635f64192c | [log] [tgz] |
---|---|---|
author | Erik Ernst <eernst@google.com> | Fri Apr 08 17:44:18 2022 +0000 |
committer | Commit Bot <commit-bot@chromium.org> | Fri Apr 08 17:44:18 2022 +0000 |
tree | 2d5bc6345e4607f54df51420b25d9fb6855cf007 | |
parent | ca59d05807dc6e54f0307dfe3bf8a13d0f609a95 [diff] |
Add test about evaluation order This CL adds a test of the evaluation order in the case where a function invocation `g(a)` or `r.g(a)` involves the invocation of a getter `g` that returns a function object, and that function object is invoked with an actual argument `a`. The expectation in the test is that evaluation occurs left-to-right in every case, with one exception: when `g` is a class instance getter (this does not apply to extension instance getters) the actual argument list is evaluated before the getter. This is the actually implemented behavior, and the specification is being updated to specify this behavior (cf. https://github.com/dart-lang/language/pull/2182). ------- Old description: A piece of technical debt which has been around for several years is the fact that the specified left-to-right evaluation order isn't implemented everywhere. In particular, with an ordinary invocation like `r.m(a)` where `m` is a getter that returns a function, the argument is evaluated before the getter is called, which is not a left-to-right ordering. This CL adds a test (with 2 libraries) where the evaluation order is detected, such that we can decide how to proceed. Change-Id: Ia2619fe6b4c4cf4cec63bac9c9f834306bdefe52 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/238903 Reviewed-by: Lasse Nielsen <lrn@google.com> Commit-Queue: Erik Ernst <eernst@google.com>
Dart is:
Optimized for UI: Develop with a programming language specialized around the needs of user interface creation.
Productive: Make changes iteratively: use hot reload to see the result instantly in your running app.
Fast on all platforms: Compile to ARM & x64 machine code for mobile, desktop, and backend. Or compile to JavaScript for the web.
Dart's flexible compiler technology lets you run Dart code in different ways, depending on your target platform and goals:
Dart Native: For programs targeting devices (mobile, desktop, server, and more), Dart Native includes both a Dart VM with JIT (just-in-time) compilation and an AOT (ahead-of-time) compiler for producing machine code.
Dart Web: For programs targeting the web, Dart Web includes both a development time compiler (dartdevc) and a production time compiler (dart2js).
Dart is free and open source.
See LICENSE and PATENT_GRANT.
Visit dart.dev to learn more about the language, tools, and to find codelabs.
Browse pub.dev for more packages and libraries contributed by the community and the Dart team.
Our API reference documentation is published at api.dart.dev, based on the stable release. (We also publish docs from our beta and dev channels, as well as from the primary development branch).
If you want to build Dart yourself, here is a guide to getting the source, preparing your machine to build the SDK, and building.
There are more documents on our wiki.
The easiest way to contribute to Dart is to file issues.
You can also contribute patches, as described in Contributing.