dart-sdk/pkg/front_end
Johnni Winther a811db5bc6 [cfe] Change MapPattern.key to Expression
The key can only be an Expression but was unneedingly wrapped in
a ConstantPattern. Since the shared type analysis only handles
map pattern keys as expressions, the expected properties of
ConstantPattern were not set. Amongst these were the static type
of the key expression, which is know passed directly to the
handleMapPatternEntry method.

Change-Id: I705fc655e440d534ccc442c9c1359c377955b3b1
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/288282
Commit-Queue: Johnni Winther <johnniwinther@google.com>
Reviewed-by: Konstantin Shcheglov <scheglov@google.com>
Reviewed-by: Chloe Stefantsova <cstefantsova@google.com>
2023-03-13 10:05:16 +00:00
..
benchmarks
lib [cfe] Change MapPattern.key to Expression 2023-03-13 10:05:16 +00:00
outline_extraction_testcases [flip-modifiers] Make tests and outline extraction tests mixins. 2023-03-08 16:11:30 +00:00
parser_testcases [cfe] Report error on : for default values 2023-03-06 19:04:55 +00:00
test [kernel] Move Pattern nodes to package:kernel 2023-03-13 08:43:07 +00:00
testcases [cfe] Change MapPattern.key to Expression 2023-03-13 10:05:16 +00:00
tool [kernel] Move Pattern nodes to package:kernel 2023-03-13 08:43:07 +00:00
analysis_options.yaml
analysis_options_no_lints.yaml
error_recovery.yaml
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 [flip-patterns] Enable "records" and "patterns" experiment flags. 2023-03-10 20:02:23 +00:00
OWNERS
PRESUBMIT.py
pubspec.yaml
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.