Johnni Winther
8103c90dbf
+ emit only one message per method given that it now always has the same root cause, namely that the combined member signature does not exist. Closes #31797 Change-Id: Id89a5557c5fdda1db087c20cbe92847dd08216a3 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/175305 Reviewed-by: Dmitry Stefantsov <dmitryas@google.com> Commit-Queue: Johnni Winther <johnniwinther@google.com>
Overview
The testcases in this directory and its subdirectory are all compiled in various different configurations designed to test various aspects of Fasta (or more generally, package:front_end).
The configurations are described below.
The source of truth for these configurations is the file pkg/front_end/testing.json.
Dart 1.0 Compilation
- Status file: legacy.status
- Standalone test: pkg/front_end/test/fasta/legacy_test.dart
- Expectation prefix:
.direct.expect - How to update expectations:
./pkg/front_end/tool/fasta testing -DupdateExpectations=true compile/test1 compile/test2 ...
Dart 1.0 Outlines
- Status file: outline.status
- Standalone test: pkg/front_end/test/fasta/outline_test.dart
- Expectation prefix:
.outline.expect - How to update expectations:
./pkg/front_end/tool/fasta testing -DupdateExpectations=true outline/test1 outline/test2 ...
Dart 2.0 (strong mode)
- Status file: strong.status
- Standalone test: pkg/front_end/test/fasta/strong_test.dart
- Expectation prefix:
.strong.expect - How to update expectations:
./pkg/front_end/tool/fasta testing -DupdateExpectations=true -DupdateComments=true strong/test1 strong/test2 ...
Note: strong mode configuration additionally parses comments in the test file and can precisely match internal details of the compiler such as the inferred type of an expression or if a warning was emitted at a given location.