b812517fac
When asking for all references of a member it starts by finding all supertypes for the class, then for each supertype (including itself) (that has a member with the same name as the one we're querying for) it searches for all subtypes. We recall that when getting all subtypes, it really gets all direct subtypes, then for each of those, their direct subtypes etc. Naturally, then, with getting all subtypes for all supertypes we will often ask for all direct subtypes of the same class several times. In fact, it's O(n^2): As an example, if asking for references to `foo` on this (in a file in analyzer, with 8 workspaces): ``` class X0 { void foo() { print('hello'); } } class X1 extends X0 { void foo() { print('hello'); } } class X2 extends X1 { void foo() { print('hello'); } } [...] class X149 extends X148 { void foo() { print('hello'); } } ``` we ask for subtypes 90600 (150 classes * 151 / 2 * 8 workspaces) times. This CL stops that from happening and in the example from above we "only" asks for subtypes 1200 (150 classes * 8 workspaces) times. For the `newFile` from `AbstractSingleUnitTest` example, for instance, we go from 28,264 asks to 17,432 asks (a ~38% reduction). Non-first runtimes when asking for references: Before: 0:00:03.074853 0:00:03.021881 0:00:03.034707 0:00:03.115596 0:00:03.032574 After: 0:00:02.223978 0:00:02.149937 0:00:02.150236 0:00:02.104704 0:00:02.175859 Difference at 95.0% confidence -0.894979 +/- 0.060283 -29.2867% +/- 1.97266% (Student's t, pooled s = 0.0413338) Change-Id: Id792a595e74de01c7186ab1263c38728f051f603 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/272623 Commit-Queue: Jens Johansen <jensj@google.com> Reviewed-by: Konstantin Shcheglov <scheglov@google.com> Reviewed-by: Brian Wilkerson <brianwilkerson@google.com> |
||
---|---|---|
.dart_tool | ||
.github | ||
benchmarks | ||
build | ||
docs | ||
pkg | ||
runtime | ||
samples | ||
sdk | ||
tests | ||
third_party | ||
tools | ||
utils | ||
.clang-format | ||
.gitattributes | ||
.gitconfig | ||
.gitignore | ||
.gn | ||
.mailmap | ||
.style.yapf | ||
.vpython | ||
AUTHORS | ||
BUILD.gn | ||
CHANGELOG.md | ||
codereview.settings | ||
CONTRIBUTING.md | ||
DEPS | ||
LICENSE | ||
OWNERS | ||
PATENT_GRANT | ||
PRESUBMIT.py | ||
README.dart-sdk | ||
README.md | ||
sdk_args.gni | ||
SECURITY.md | ||
WATCHLISTS |
Dart
A client-optimized language for fast apps on any platform
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).
License & patents
Dart is free and open source.
See LICENSE and PATENT_GRANT.
Using Dart
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).
Building Dart
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.
Contributing to Dart
The easiest way to contribute to Dart is to file issues.
You can also contribute patches, as described in Contributing.