523f03a749
This CL adds `isWildcard` to `StructuralVariableBuilder` and allows type variables in functions and function types. It also removes them from scope so they can't be used. Bug: https://github.com/dart-lang/sdk/issues/55655 Change-Id: I26237375480318dd0c9a01cb59b3426b783ca7be Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/372240 Reviewed-by: Johnni Winther <johnniwinther@google.com> Commit-Queue: Kallen Tu <kallentu@google.com> Reviewed-by: Chloe Stefantsova <cstefantsova@google.com> |
||
|---|---|---|
| .. | ||
| class_modifiers | ||
| const_functions | ||
| constructor_tearoffs | ||
| dart2js | ||
| dart2wasm | ||
| dartdevc | ||
| dartino | ||
| enhanced_enums | ||
| expression | ||
| extension_types | ||
| extensions | ||
| general | ||
| generic_metadata | ||
| implicit_getter_calls | ||
| incremental | ||
| inference | ||
| inference_new | ||
| inference_update_1 | ||
| inference_update_2 | ||
| inference_update_3 | ||
| instantiate_to_bound | ||
| late_lowering | ||
| late_lowering_sentinel | ||
| macros | ||
| named_arguments_anywhere | ||
| nnbd | ||
| no_such_method_forwarders | ||
| none | ||
| nonfunction_type_aliases | ||
| offsets | ||
| patterns | ||
| rasta | ||
| records | ||
| regress | ||
| runtime_checks | ||
| runtime_checks_new | ||
| sealed_class | ||
| set_literals | ||
| static_field_lowering | ||
| super_parameters | ||
| triple_shift | ||
| unified_collections | ||
| unscheduled_experiments | ||
| variance | ||
| wildcard_variables | ||
| expression.status | ||
| incremental.status | ||
| incremental_bulk_compiler_full.status | ||
| incremental_bulk_compiler_smoke.status | ||
| incremental_dartino.status | ||
| modular.status | ||
| outline.status | ||
| OWNERS | ||
| README.md | ||
| sdk.status | ||
| strong.status | ||
| textual_outline.status | ||
| weak.status | ||
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.
Updating all expectations
To update test expectations for all tests at once, run:
dart pkg/front_end/tool/update_expectations.dart
Note that this takes a long time and should only be used when many tests need updating.
Updating expectations for a single test
To update the expectations for a specific test, provide the folder and test name as an argument.
For example, if you want to update the test expectations for a test, such as pkg/front_end/testcases/general/abstract_instantiation.dart, then run:
dart pkg/front_end/tool/update_expectations.dart general/abstract_instantiation
Updating expectations for all tests in a folder
If you want to update the test expectations for a specific folder of tests such as the pkg/front_end/testcases/general/ folder, then run:
dart pkg/front_end/tool/update_expectations.dart general/...
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.