6f16174d56
- Remove collecting private fields from scope calculation We only need to collect the fields from the evaluated expression and they are already collected separately. - Correct private fields calculation Currently, library names are assumed to be the same as the module, which creates redefinitions of library variable in produced Javascript code, and exceptions in chrome for modules that contain more than one library. The actual fix will come from making DDC incremental by storing more information, for now make a best effort to compute correct names for library variables from the module data that expression compiler receives from chrome. The following code will be produced to calculate private symbols _pf1 (from lib1, module1) and _pf2 (from lib2 module1): let lib1 = require('module1.dart').lib1; let lib2 = require('module1.dart').lib2; let _pf1 = dart.privateNames(lib1, '_pf1'); let _pf2 = dart.privateNames(lib2, '_pf2'); Note that this seems to work even if the current breakpoint is inside the define statement for lib1, and the lib1 symbol is not exported yet. Closes: https://github.com/dart-lang/sdk/issues/40272 Closes: https://github.com/dart-lang/sdk/issues/41585 Change-Id: I141719d2d5d5c08dd3c0ef5f0406756dce5575ab Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/145307 Reviewed-by: Sigmund Cherem <sigmund@google.com> Commit-Queue: Anna Gringauze <annagrin@google.com> |
||
---|---|---|
.dart_tool | ||
.github | ||
benchmarks | ||
build | ||
client | ||
docs | ||
pkg | ||
runtime | ||
samples | ||
samples-dev/swarm | ||
sdk | ||
sdk_nnbd | ||
tests | ||
third_party | ||
tools | ||
utils | ||
.clang-format | ||
.gitattributes | ||
.gitconfig | ||
.gitignore | ||
.gn | ||
.mailmap | ||
.packages | ||
.style.yapf | ||
.vpython | ||
AUTHORS | ||
BUILD.gn | ||
CHANGELOG.md | ||
codereview.settings | ||
CONTRIBUTING.md | ||
DEPS | ||
LICENSE | ||
PATENT_GRANT | ||
PRESUBMIT.py | ||
README.dart-sdk | ||
README.md | ||
sdk_args.gni | ||
WATCHLISTS |
Dart
A client-optimized language for fast apps on any platform
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).
License & patents
Dart is free and open source.
See LICENSE and PATENT_GRANT.
Using Dart
Visit the dart.dev to learn more about the language, tools, getting started, and more.
Browse pub.dev for more packages and libraries contributed by the community and the Dart team.
Building Dart
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.
Contributing to Dart
The easiest way to contribute to Dart is to file issues.
You can also contribute patches, as described in Contributing.