1a23ff68a5
The behavioral difference is that named and optional arguments are filled in with their default values in the `Invocation` object passed to `noSuchMethod`. On the implementation side we make NSM forwarders concrete and fill in their bodies in the CFE. The custom (and somewhat hacky) VM support is no longer needed, and Dart2JS can benefit from this implementation as well. According to discussion on #33031 we will be able to re-land this soon without breaking Mockito. Prior failures on precompiler bots are fixed in Patchset 2. Change-Id: If1b7fe4cf6da5ef38f330e1ad226121bcfc958a1 Reviewed-on: https://dart-review.googlesource.com/54401 Commit-Queue: Samir Jindel <sjindel@google.com> Reviewed-by: Dmitry Stefantsov <dmitryas@google.com> |
||
|---|---|---|
| .. | ||
| benchmarks/ikg | ||
| lib/src | ||
| test | ||
| testcases | ||
| tool | ||
| analysis_options.yaml | ||
| error_recovery.yaml | ||
| LICENSE | ||
| messages.status | ||
| messages.yaml | ||
| pubspec.yaml | ||
| README.md | ||
| testing.json | ||
Front end for Dart
This package provides a low-level API for use by compiler back ends that wish to implement the Dart language. It is intended for eventual use by dev_compiler, dart2js, and the Dart VM. In addition, it will share implementation details with the analyzer package--this will be accomplished by having the analyzer package import (and re-export) parts of this package's private implementation.
End-users should use the [dartanalyzer][analyzercli] command-line tool to analyze their Dart code.
Integrators that want to write tools that analyze Dart code should use the [analyzer] package.
Note: The APIs in this package are in an early state; developers should be careful about depending on this package. In particular, there is no semver contract for release versions of this package. Please depend directly on individual versions.