languages/dart-sdk
languages/dart-sdk
1
0
Fork 0
mirror of https://github.com/dart-lang/sdk synced 2024-07-25 04:15:45 +00:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity
dart-sdk/pkg/front_end
History
Johnni Winther ced5b4e25d [cfe] Ensure nullable result type for ??= for effect 
Closes #54069

Change-Id: I4caaad1b86f9ef68f1d36d7b2f9afc92364ce83c
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/336662
Reviewed-by: Chloe Stefantsova <cstefantsova@google.com>
Commit-Queue: Johnni Winther <johnniwinther@google.com>
2023-11-17 14:06:50 +00:00
..
benchmarks
lib [cfe] Ensure nullable result type for ??= for effect 2023-11-17 14:06:50 +00:00
outline_extraction_testcases
parser_testcases Fix incorrect file reference in license headers 2023-09-18 06:44:08 +00:00
test [cfe] Ensure nullable result type for ??= for effect 2023-11-17 14:06:50 +00:00
testcases [cfe] Ensure nullable result type for ??= for effect 2023-11-17 14:06:50 +00:00
tool analyzer: Move the Source class to be public API. 2023-11-14 17:10:37 +00:00
analysis_options.yaml Replace deprecated lint rules in front-end packages 2023-05-23 14:01:49 +00:00
analysis_options_no_lints.yaml [cfe] Add CFE test for DartScope 2023-11-15 10:17:23 +00:00
error_recovery.yaml
LICENSE
messages.status [cfe] Report an error on optional positional or named parameters in extension type declarations 2023-10-25 10:26:38 +00:00
messages.yaml Reland "Expire 3.0.0 experiment flags." 2023-11-17 13:10:01 +00:00
OWNERS
PRESUBMIT.py
pubspec.yaml Enable private field promotion in pkg/front_end 2023-09-18 15:39:47 +00:00
README.md
testing.json [cfe,ddc] Add tests for scopes in extensions, extension types and mixins 2023-11-16 09:37:31 +00:00
testing_with_lints.json Fix incorrect file reference in license headers 2023-09-18 06:44:08 +00:00

README.md

Front end for Dart

This package provides a low-level API for use by compiler back ends that wish to implement the Dart language. It is intended for eventual use by dev_compiler, dart2js, and the Dart VM. In addition, it will share implementation details with the analyzer package--this will be accomplished by having the analyzer package import (and re-export) parts of this package's private implementation.

End-users should use the dart analyze command-line tool to analyze their Dart code.

Integrators that want to write tools that analyze Dart code should use the analyzer package.

Note: A previous version of this package was published on pub.dev. It has now been marked DISCONTINUED as it is not intended for direct consumption, as per the notes above.