dart-sdk/pkg/front_end
Johnni Winther d451cb64c0 [_fe_analyzer_shared] Only show fields of interest in exhaustiveness tests
Only the fields of a scrutinee type that are used in the cases are
now shown in the test expectations. When the field is not present,
for instance when the scrutinee type is nullable, or the fields are
only present on (some of) the subtype of the scrutinee type, the
fields are shown to be missing with a `-`.

Change-Id: I2d36b230e979dc929d083cfb8f9cdb9f1143d380
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/287280
Reviewed-by: Paul Berry <paulberry@google.com>
Commit-Queue: Johnni Winther <johnniwinther@google.com>
2023-03-08 07:14:47 +00:00
..
benchmarks
lib [_fe_shared_analyzer] Use internal constant-to-text 2023-03-07 18:52:23 +00:00
outline_extraction_testcases
parser_testcases [cfe] Report error on : for default values 2023-03-06 19:04:55 +00:00
test [_fe_analyzer_shared] Only show fields of interest in exhaustiveness tests 2023-03-08 07:14:47 +00:00
testcases [flip-modifiers] Make more tests use mixin instead of class. 2023-03-07 23:59:39 +00:00
tool [kernel] Shift up specialized kernel tags 2023-02-21 15:21:38 +00:00
analysis_options.yaml Generate a diagnostic for language overrides prior to 2.12 2023-01-10 05:27:48 +00:00
analysis_options_no_lints.yaml
error_recovery.yaml Spelling 2023-01-30 18:29:59 +00:00
LICENSE
messages.status [cfe/flip-modifiers] Remove error for Function completely. Rely on its modifier errors. 2023-03-07 08:13:19 +00:00
messages.yaml [cfe/flip-modifiers] Remove error for Function completely. Rely on its modifier errors. 2023-03-07 08:13:19 +00:00
OWNERS
PRESUBMIT.py
pubspec.yaml [pkg/vm] Initial work on constant operating system fields and getters. 2023-02-10 16:29:50 +00:00
README.md
testing.json
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.