[vm/concurrency] Move boxed field list form Isolate to IsolateGroup As part of making the compiler independent of a particular isolate (since all isolates in a group share the same JITed code) we move the boxed field list to IsolateGroup. Any isolate that hits the lazy compile stub will then drain the fields to be deoptimized and performs that work. A follow-up investigation can decide whether it's beneficial (or hurtful) for single vs multi isolate scenarios to deoptimize the field immediately in BG compiler (and interrupt mutator). It is possibly disadvantagues for single isolate scenarios to do so, since it causes more mutator interruptions. Issue https://github.com/dart-lang/sdk/issues/36097 TEST=Refactoring of existing code. Change-Id: I64b42ad99056b43a7264bcc30280b9ba39389a2e Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/182505 Commit-Queue: Martin Kustermann <kustermann@google.com> Reviewed-by: Ryan Macnak <rmacnak@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.