[analyzer] LSP 'get implementations': get lineInfo directly Asking for implementations of 'ToJsonable' from package:analysis_server/lsp_protocol/protocol_special.dart takes 8+ seconds both on first request and on subsequent requests. Turns out most of that is spent on getting line info data for each result via `server.getLineInfo`. This CL rewrites how the search is performed, getting all subtypes directly via `searchAllSubtypes`, from which one can cheaply get the line info. On my machine, the call that always took 8+ seconds before now takes <2 seconds (at least on subsequent runs). Notice that the time also depends on how much is open by the editor and that calls from my editor with many folders open still takes ~6 seconds. This CL furthermore adds more performance measurements that's available via the "Analysis Server Diagnostics" page "Timing" for "textDocument/implementation" requests. Change-Id: I2e5ef20238901fb4734cc182aeb53adfc96f79b6 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/272360 Commit-Queue: Jens Johansen <jensj@google.com> Reviewed-by: Konstantin Shcheglov <scheglov@google.com>
Dart is:
Optimized for UI: Develop with a programming language specialized around the needs of user interface creation.
Productive: Make changes iteratively: use hot reload to see the result instantly in your running app.
Fast on all platforms: Compile to ARM & x64 machine code for mobile, desktop, and backend. Or compile to JavaScript for the web.
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.