| commit | d1b9a93363f252b8f397d2f2c9d5e54bbb18347d | [log] [tgz] |
|---|---|---|
| author | Alexander Markov <alexmarkov@google.com> | Thu May 14 16:40:22 2020 +0000 |
| committer | commit-bot@chromium.org <commit-bot@chromium.org> | Thu May 14 16:40:22 2020 +0000 |
| tree | 9b95a91d2d45eeb585b02e741c20130f3938c44a | |
| parent | 2676764792b2170b5f7867600a2144e7493fa950 [diff] |
Revert "[vm/nnbd] Auto-detect null-safety from entry point in kernel compilers" This reverts commit fd19c8cc255e2cbf584f6b37bff515624aa0ba58. Reason for revert: Flutter has tests with --enable-experiment=non-nullable, but dart:ui is not migrated yet and gen_snapshot doesn't detect null-safety from kernel file. This change causes failures in those tests as dill file is now compiled with null-safety enabled due to the auto-detection. Original change's description: > [vm/nnbd] Auto-detect null-safety from entry point in kernel compilers > > If --null-safety flag is not specified, tools should infer null safety > mode from a legacy status of an entry point script. > This change adds such auto-detection to kernel compilers (front-end > server and gen_kernel). > > Issue: https://github.com/dart-lang/sdk/issues/41206 > Change-Id: If78491d08390c28b98e86857ec7d61520433dee9 > Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/148024 > Reviewed-by: Ryan Macnak <rmacnak@google.com> > Reviewed-by: Alexander Aprelev <aam@google.com> > Commit-Queue: Alexander Markov <alexmarkov@google.com> TBR=aam@google.com,rmacnak@google.com,alexmarkov@google.com,asiva@google.com Change-Id: Ie6105552c9d88101a3188f5daec4ee9a9c24a530 No-Presubmit: true No-Tree-Checks: true No-Try: true Issue: https://github.com/dart-lang/sdk/issues/41206 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/148141 Reviewed-by: Alexander Markov <alexmarkov@google.com> Commit-Queue: Alexander Markov <alexmarkov@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 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.
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.