mirror of
https://github.com/dart-lang/sdk
synced 2024-09-16 03:47:13 +00:00
Remove dead/outdated lints from pkg/dev_compiler/README.md
Change-Id: I6f09fcc5e8627b22e2a1e14568218108501ffa8f Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/99640 Auto-Submit: Kevin Moore <kevmoo@google.com> Reviewed-by: Jenny Messerly <jmesserly@google.com> Commit-Queue: Jenny Messerly <jmesserly@google.com>
This commit is contained in:
parent
9d15138c91
commit
9a5a720413
|
@ -1,15 +1,8 @@
|
|||
dev_compiler
|
||||
============
|
||||
|
||||
[![Build Status](https://travis-ci.org/dart-lang/sdk.svg?branch=master)](https://travis-ci.org/dart-lang/sdk)
|
||||
|
||||
The Dart Dev Compiler (DDC) is a fast, modular compiler that generates modern JavaScript (EcmaScript 6). Its primary use today is to support fast, iterative development of Dart web applications for Chrome and other modern browsers.
|
||||
|
||||
Most users will use DDC via [pub](https://webdev.dartlang.org/tools/pub/pub-serve). It is supported by pub starting with the Dart 1.24 release.
|
||||
|
||||
# Soundness and Restrictions
|
||||
|
||||
DDC is built upon Dart's new [strong mode](STRONG_MODE.md) type system. It only compiles programs that statically type check (i.e., no strong mode errors). It leverages static type checking to generate simpler, readable, and more idiomatic code with fewer runtime checks. In general, DDC is able to provide stronger type guarantees - i.e., *soundness* - than traditional Dart checked mode with significantly fewer runtime checks.
|
||||
DDC is built upon Dart's [sound](https://www.dartlang.org/guides/language/sound-dart) type system. It only compiles programs that statically type check (i.e., no strong mode errors). It leverages static type checking to generate simpler, readable, and more idiomatic code with fewer runtime checks. In general, DDC is able to provide stronger type guarantees - i.e., *soundness* - than traditional Dart checked mode with significantly fewer runtime checks.
|
||||
|
||||
With strong mode, DDC is stricter than traditional Dart production mode or checked mode. Running existing Dart code on DDC will generally require fixing both static and runtime type errors.
|
||||
|
||||
|
@ -28,17 +21,11 @@ List<Object> list2 = list; // Generics are covariant. No runtime check require
|
|||
List<int> list3 = list2; // Implicit runtime downcast triggers error.
|
||||
```
|
||||
|
||||
See the [strong mode documentation](STRONG_MODE.md) for more details.
|
||||
|
||||
# Modularity
|
||||
|
||||
DDC provides fast, incremental compilation based on standard JavaScript modules. Unlike Dart2JS, DDC does not require an entire Dart application. Instead, it operates modularly: it compiles a set of Dart files into a JavaScript module. A DDC compilation step requires a set of input Dart files and a set of *summaries* of dependencies. It performs modular type checking as part of this compilation step, and, if the input type checks, it generates a JavaScript module (e.g., [*ES6*](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/import), [*AMD*](https://github.com/amdjs/amdjs-api/blob/master/AMD.md), or [*CommonJS*](https://nodejs.org/docs/latest/api/modules.html)). The browser (i.e., the JavaScript runtime) loads and links the generated modules when running the application.
|
||||
During development, a compilation step only needs to be rerun if the Dart files or summaries it relies upon change. For most changes, only a very small part of your code will require recompilation. Moreover, modules that are unchanged can be cached in the browser.
|
||||
|
||||
Most users invoke DDC indirectly via [pub](https://webdev.dartlang.org/tools/pub/pub-serve). Pub computes module structure and build steps automatically and invoke DDC accordingly. Pub configures DDC to use AMD modules and uses the standard [AMD `require.js` loader](http://requirejs.org/) to bootstrap and load the application.
|
||||
|
||||
More advanced users may want to configure or invoke DDC directly. In general, the mapping of Dart files to JS modules is flexible. The key requirement is that module dependencies (i.e., `require` in AMD or CommonJS or `import` in ES6) must be acyclic. In practice, this means that individual Dart libraries cannot each be mapped to a corresponding JS module (as Dart imports can be and often are cyclic). See the [usage document](USAGE.md) for more details.
|
||||
|
||||
# EcmaScript 6
|
||||
|
||||
DDC attempts to map Dart to idiomatic EcmaScript 6 (ES6) as cleanly as possible, and it relies heavily on static typing to do this. In general, where Dart concepts map directly to ES6, DDC generates code accordingly. For example, Dart classes are mapped to ES6 classes, Dart fields to ES6 properties, Dart getters/setters to ES6 getters/setters, Dart methods to ES6 methods, and so on. In most cases, names are preserved and calling conventions are natural JavaScript ones.
|
||||
|
|
Loading…
Reference in a new issue