| commit | 867611b4f12bf357284289ad9b2abf83b780ddec | [log] [tgz] |
|---|---|---|
| author | Danny Tuppeny <danny@tuppeny.com> | Thu Jul 25 14:41:58 2024 +0000 |
| committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Jul 25 14:41:58 2024 +0000 |
| tree | 17a23a7a84a26ca9886fe57e773710b253025e1b | |
| parent | f4477452952b2174627dd7489520f2acaef6e36f [diff] |
[analysis_server] Prevent the InlayHints handler from locking requests when obtaining a resolved unit Instead, obtain a resolved unit and then verify the versions still match (and if not, reject the request as stale). This doesn't eliminate the possibility of a deadlock because the completion handler still does the same - however it's much less likely that completion is running during server initialization (whereas inlay hints for an open file can happen early) and rejecting requests during typing may have more of an impact there (where the user is often typing, and the editor may be compensating for their changes, so a "stale" response may be better than constantly restarting). If we make changes to scheduling on the server, the ability to pause incoming _requests_ without also pausing incoming _responses_ may provide the best of both worlds here. Fixes https://github.com/dart-lang/sdk/issues/56311 Change-Id: I34412356da444e8c57f38ebe0d821c805179b0b2 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/377642 Commit-Queue: Brian Wilkerson <brianwilkerson@google.com> Reviewed-by: Brian Wilkerson <brianwilkerson@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.