| commit | 41612e437559b3b626397f0f82d4c3c275a54541 | [log] [tgz] |
|---|---|---|
| author | Danny Tuppeny <danny@tuppeny.com> | Wed Mar 27 21:20:06 2024 +0000 |
| committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Mar 27 21:20:06 2024 +0000 |
| tree | b6bc7e69ed571d6b357000517f95b0ec54421344 | |
| parent | 16589e650e88e8f8b42e2de827d630b571a8491a [diff] |
[analysis_server] Ensure server notifications are sent for newly-opened files whose contents are unmodified Some time ago I implemented an optimisation to skip analysis when a file is opened in the LSP server if the contents exactly matched what was last analyzed from disk (since it would just produce the same results). Some notifications (like Outline) are only sent for open files and are triggered by analysis results. Skipping analysis means that some notifications would not be sent when you first open a file (because no new analysis result was computed). This became quite noticable with the new CodeLenses because there are other CodeLenses (built into the Dart-Code extension) that were relying on Outline notifications and would "time out" after 5s, and this had the effect of causing the new CodeLenses to not appear for 5s (because VS Code waits for all CodeLenses). This wasn't obvious before because of the caching VS Code does for CodeLens locations. Fixes https://github.com/Dart-Code/Dart-Code/issues/5048 Change-Id: I5653c01fe7b224ba693f5b95a8af8e3c3d3da06d Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/360041 Reviewed-by: Brian Wilkerson <brianwilkerson@google.com> Reviewed-by: Konstantin Shcheglov <scheglov@google.com> Commit-Queue: Brian Wilkerson <brianwilkerson@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.