dart-sdk/pkg/front_end
Johnni Winther 43452cdd6c [cfe] Remove SourceLibraryBuilder.libraryTypeParameterScopeBuilderForTesting
This helps moving `currentTypeParameterScopeBuilder` and
`_libraryTypeParameterScopeBuilder` to SourceCompilationUnitImpl

Change-Id: I1374accef8e177a4572bf21ad839a105ced91395
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/372900
Reviewed-by: Jens Johansen <jensj@google.com>
Commit-Queue: Johnni Winther <johnniwinther@google.com>
2024-06-24 10:01:28 +00:00
..
benchmarks [cfe] Add least supported version check of 2.12 2024-05-08 09:28:45 +00:00
lib/src [cfe] Remove SourceLibraryBuilder.libraryTypeParameterScopeBuilderForTesting 2024-06-24 10:01:28 +00:00
outline_extraction_testcases
parser_testcases [parser] Add more tokens 2024-06-24 08:12:41 +00:00
test [parser] Add more tokens 2024-06-24 08:12:41 +00:00
testcases [cfe] Local and top level function wildcard type parameters are non-binding. 2024-06-21 17:59:29 +00:00
tool [CFE] Fix outline_suite time-regression on using generateKernelInternal in expectation tests 2024-06-21 10:06:08 +00:00
analysis_options.yaml
analysis_options_no_lints.yaml
error_recovery.yaml
LICENSE
messages.status [dart:js_interop] Add static error for converted functions that contain named params 2024-06-14 19:42:10 +00:00
messages.yaml [dart:js_interop] Add static error for converted functions that contain named params 2024-06-14 19:42:10 +00:00
OWNERS
PRESUBMIT.py
presubmit_helper.dart [CFE] Fix lint_suite not ignoring exports in api_unstable in presubmit 2024-06-21 10:07:29 +00:00
presubmit_helper_spawn.dart
pubspec.yaml add package:_macros (SDK vendored) and package:macros (pub published) 2024-03-26 18:40:00 +00:00
README.md
testing.json [cfe] Move fasta/codes/ to src/ and rename to cfe_codes* 2024-06-20 09:36:39 +00:00
testing_with_lints.json

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.