| commit | 741d101852d59e6e10b5f8be0b058648c37d4883 | [log] [tgz] |
|---|---|---|
| author | Konstantin Shcheglov <scheglov@google.com> | Fri Sep 26 08:44:52 2025 -0700 |
| committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Sep 26 08:44:52 2025 -0700 |
| tree | bc0f6c96e3581c403defd6846c7d036159c97d0f | |
| parent | dee968bcd81af2853a3a464a1ca91f18469df468 [diff] |
Fine. Add toBytes/fromBytes for manifests; simplify isSatisfied Introduce canonical binary helpers for fine-grained artifacts and reduce boilerplate at call sites. What’s changed - LibraryManifest: add `toBytes()` and `fromBytes(Uint8List)` that handle table setup (`initFromTableTrailer`) and trailer writing. - RequirementsManifest: add the same `toBytes()` / `fromBytes()` helpers. - RequirementsManifest.assertSerialization(): switch to the new helpers to guarantee byte-for-byte round-trip equality. - LibraryManifestBuilder._assertSerialization(): likewise, use the new helpers instead of inlined writer/reader logic. - RequirementsManifest.isSatisfied(): remove the unused `libraryManifests` parameter; the method now takes only `elementFactory`. Update all call sites: - analysis/driver.dart: `_getLibraryDiagnosticsBundle()` - analysis/library_context.dart: `_getLinkedBundleEntry()` Why - Centralizes binary encoding/decoding, ensuring consistent use of string and ID tables and avoiding subtle mismatches. - Eliminates duplicated serialization snippets and the risk of forgetting to write/read the table trailer. - Simplifies the requirements API by removing a parameter that was no longer needed. Notes - No functional behavior change is intended beyond the API signature adjustment. Change-Id: I1f34e40ac40dbc426cecc3cf16962247bbc285e0 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/451545 Reviewed-by: Johnni Winther <johnniwinther@google.com> Commit-Queue: Konstantin Shcheglov <scheglov@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 in our repo at docs.
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.