| commit | 53030709a500bee517d3a7fa960df9dc188c1287 | [log] [tgz] |
|---|---|---|
| author | Fedor Shcheglov <fedor.scheglov@gmail.com> | Fri Aug 08 12:36:50 2025 -0700 |
| committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Aug 08 12:36:50 2025 -0700 |
| tree | b90d989ef4298dcd9a18221adb62c518597a6555 | |
| parent | aba11d07af29176db9520ef1fd74e72056116075 [diff] |
Remove redundant firstTokenOffset nulls across fragments `firstTokenOffset` was required but always passed as `null` and later filled by `InformativeDataApplier`, making the API noisy and misleading. Made optional in: - FragmentImpl - ExecutableFragmentImpl - FieldFormalParameterFragmentImpl - FormalParameterFragmentImpl - FunctionFragmentImpl - GenericFunctionTypeFragmentImpl - NonParameterVariableFragmentImpl - PropertyAccessorFragmentImpl - SuperFormalParameterFragmentImpl - TypeParameterFragmentImpl Removed from constructors of: - ClassFragmentImpl - ConstructorFragmentImpl - EnumFragmentImpl - ExtensionFragmentImpl - ExtensionTypeFragmentImpl - FieldFragmentImpl - GetterFragmentImpl - InstanceFragmentImpl - InterfaceFragmentImpl - MethodFragmentImpl - MixinFragmentImpl - PropertyInducingFragmentImpl - TopLevelFunctionFragmentImpl - TopLevelVariableFragmentImpl All call sites across builders, readers, utilities, and tests were updated to stop passing `firstTokenOffset: null`. Behavior is unchanged: offsets continue to be computed and applied by `InformativeDataApplier`. This reduces boilerplate and clarifies the construction contract for synthetic and derived elements. Change-Id: Iba07f919b88b0bf585bfec0c5b8f4cbbe5214459 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/444389 Commit-Queue: Paul Berry <paulberry@google.com> Reviewed-by: Paul Berry <paulberry@google.com> Reviewed-by: 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.