0689ec527a
I don't like having a large volume of Dart code sitting under tools/ where it is hard to analyze, lint, test, and reuse. Also, eventually we want to merge test.dart and test.py. This seems like an easy mostly mechanical first step. All I did was: 1. Move the contents of tools/test.dart to pkg/test_runner/lib/test_runner.dart. (That's not a great file name since we already have pkg/test_runner/bin/test_runner.dart, but it was the best I could come up with. 2. Copy tools/bots/results to pkg/test_runner/bot_results.dart. I don't like duplicating this, but there are other scripts under tools that import the old location. Eventually, we should have those scripts import it from package:test_runner/bot_results.dart, but I didn't want to do that here since I'm not familiar with those other scripts. 3. Make tools/test.dart import and forward to pkg/test_runner/lib/test_runner.dart. 4. Fix any linter and type errors. The test_runner package has a bunch of strictness checks and lints enable to keep it cleaner. 5. Run dartfmt --fix to format and get rid of "new", etc. Change-Id: Ifc89817508d3fc147fa78dbc6744d547aeaf4c55 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/155240 Commit-Queue: Bob Nystrom <rnystrom@google.com> Auto-Submit: Bob Nystrom <rnystrom@google.com> Reviewed-by: Jonas Termansen <sortie@google.com> |
||
---|---|---|
.dart_tool | ||
.github | ||
benchmarks | ||
build | ||
client | ||
docs | ||
pkg | ||
runtime | ||
samples | ||
samples-dev/swarm | ||
sdk | ||
tests | ||
third_party | ||
tools | ||
utils | ||
.clang-format | ||
.gitattributes | ||
.gitconfig | ||
.gitignore | ||
.gn | ||
.mailmap | ||
.packages | ||
.style.yapf | ||
.vpython | ||
AUTHORS | ||
BUILD.gn | ||
CHANGELOG.md | ||
codereview.settings | ||
CONTRIBUTING.md | ||
DEPS | ||
LICENSE | ||
PATENT_GRANT | ||
PRESUBMIT.py | ||
README.dart-sdk | ||
README.md | ||
sdk_args.gni | ||
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 the dart.dev to learn more about the language, tools, getting started, and more.
Browse pub.dev for more packages and libraries contributed by the community and the Dart team.
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.