[vm] Simplify root unit checks in snapshot deserialization. Previously, there were two ways to determine whether a deserialization cluster was being deserialized for the root loading unit or a non-root loading unit: * some deserialization clusters (those deriving from CanonicalSetDeserializationCluster) took a boolean at construction time, and * all deserialization clusters took an additional boolean argument to ReadFill and PostLoad on whether the loading unit was primary (i.e., the root) or not. Since only clusters that deal with canonical values need to worry about whether the deserializing loading unit is the root or not, standardize on the first, where clusters that need to know take the boolean in their constructor and store it in a field, and remove the boolean argument to ReadFill and PostLoad. Have DeserializationCluster::PostLoad just check is_canonical() to determine whether to throw an error if not overridden in the base class, so that any deserialization cluster that may operate on canonical objects needs to explicitly make a choice about whether they need to recanonicalize or not. This check only happens in the precompiled runtime, as otherwise there are no non-root loading units. In particular, this fixes an issue where symbols (canonical strings) in non-root loading units weren't marked as canonical, even though they do not need recanonicalization (since symbol tables are per-isolate group, and thus per-loading unit). TEST=ci (refactoring, test of symbol fix coming in followup CL) Cq-Include-Trybots: luci.dart.try:vm-aot-dwarf-linux-product-x64-try,vm-aot-linux-release-x64-try,vm-aot-linux-debug-x64-try,vm-aot-mac-release-arm64-try,vm-aot-mac-product-arm64-try Change-Id: I411a254767653da82631abc1fcc687ae4259e0b4 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/363321 Commit-Queue: Tess Strickland <sstrickl@google.com> Reviewed-by: Ryan Macnak <rmacnak@google.com>
Dart is:
Approachable: Develop with a strongly typed programming language that is consistent, concise, and offers modern language features like null safety and patterns.
Portable: Compile to ARM, x64, or RISC-V machine code for mobile, desktop, and backend. Compile to JavaScript or WebAssembly for the web.
Productive: Make changes iteratively: use hot reload to see the result instantly in your running app. Diagnose app issues using DevTools.
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.
Future plans for Dart are included in the combined Dart and Flutter roadmap on the Flutter wiki.