| commit | 2aea88f002cfe1390fd1db69942e406a2e79f217 | [log] [tgz] |
|---|---|---|
| author | Konstantin Shcheglov <scheglov@google.com> | Tue Aug 26 09:06:30 2025 -0700 |
| committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Aug 26 09:06:30 2025 -0700 |
| tree | 8088d8859bf8c2d81f46df277057c643d6889281 | |
| parent | 38a6261ee89c3ae8efe828288d6038516d38f1c3 [diff] |
Fine. Make ManifestItemId use a monotonic 64-bit counter Replace `(timestamp, randomBits)` with a lexicographically ordered `(hi32, lo32)` pair to generate IDs from a monotonic counter rather than wall time. `lo32` is a 32-bit counter seeded from the current time and incremented modulo 2^32; `hi32` increments only when `lo32` wraps. This removes dependence on low-resolution timers (notably on Windows) that could produce non-monotonic ordering when many IDs were generated in the same tick. Within a process, IDs are now strictly increasing. Notable changes: * Update `generate()` to bump `lo32` and carry into `hi32` on wrap. * Rename fields to `hi32`/`lo32`; update equality, hash, and compare. * Keep serialization as two `UInt32`s, now writing `hi32` then `lo32`. (This alters on-disk semantics; existing caches may need invalidation.) * Simplify `toString()` to print the `(hi32, lo32)` tuple. This change improves determinism and ordering guarantees without relying on platform timer resolution. Cross-run ordering is no longer tied to wall time and may differ from prior behavior. Change-Id: Ib3b1196ca3f6714a90dd2f1847e6e8b9a7bad957 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/446701 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.