dev_compiler: cleanup outdated URLs

dartlang.org -> dart.dev
Remove references to dev-compiler group that has been deleted

Change-Id: I8d994b5f2dba19aab3c3b0fc16c5c340fbce80fd
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/167442
Auto-Submit: Kevin Moore <kevmoo@google.com>
Reviewed-by: Nicholas Shahan <nshahan@google.com>
This commit is contained in:
Kevin Moore 2020-10-13 20:06:28 +00:00
parent cddea627a7
commit 98a21f44d5
3 changed files with 6 additions and 9 deletions

View file

@ -2,9 +2,9 @@ The Dart Dev Compiler (DDC) is a fast, modular compiler that generates modern Ja
# Soundness and Restrictions
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.
DDC is built upon Dart's [sound](https://dart.dev/guides/language/type-system) 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.
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.
For example, although the following snippet will run in production or checked mode, it will fail to compile with DDC:

View file

@ -79,6 +79,3 @@ change. If you find issues, please let us know.
Please file issues in our [GitHub issue
tracker](https://github.com/dart-lang/sdk/issues).
You can also view or join our [mailing
list](https://groups.google.com/a/dartlang.org/forum/#!forum/dev-compiler).

View file

@ -54,7 +54,7 @@ analyzer:
With strong mode, we want to provide stronger typing while preserving the
terseness of Dart. [Idiomatic Dart
code](https://www.dartlang.org/effective-dart/) discourages type annotations
code](https://dart.dev/guides/language/effective-dart) discourages type annotations
outside of API boundaries, and user shouldn't have to add more types to get
better checking. Instead, strong mode uses type inference.
@ -443,7 +443,7 @@ main() {
}
```
This option is experimental and may be changed or removed in the future. Feedback is appreciated! Contact us at our [mailing list](https://groups.google.com/a/dartlang.org/forum/#!forum/dev-compiler).
This option is experimental and may be changed or removed in the future.
Try it out in your project by editing .analysis_options:
```yaml
@ -505,7 +505,7 @@ class C extends Iterable<dynamic> { /* ... */ }
This feature is to prevent accidental use of `dynamic` in code that does not intend to use it.
This option is experimental and may be changed or removed in the future. Feedback is appreciated! Contact us at our [mailing list](https://groups.google.com/a/dartlang.org/forum/#!forum/dev-compiler).
This option is experimental and may be changed or removed in the future.
Try it out in your project by editing .analysis_options:
```yaml
@ -527,4 +527,4 @@ dartanalyzer --strong --no-implicit-dynamic my_app.dart
`is` and `as` checks trigger runtime errors. We are considering introducing static
errors for these cases.
[dartspec]: https://www.dartlang.org/docs/spec/ "Dart Language Spec"
[dartspec]: https://dart.dev/guides/language/spec "Dart Language Spec"