Files

T

Johnni Winther a8f9f08253 [cfe] Don't find unnamed mixin application in least upper bound

InterfaceType's referring to unnamed mixin applications continuously
cause problems for backends since these might not correspond to
types supported at runtime. The LUB specification does not mention
how to handle these so it is valid skip these in the computation of
LUB.

Change-Id: I38f46bf43d5858dec473c26326b741cf36eb57d8
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/145420
Commit-Queue: Johnni Winther <johnniwinther@google.com>
Reviewed-by: Dmitry Stefantsov <dmitryas@google.com>

2020-09-09 13:00:17 +00:00

benchmarks/ikg

…

lib/src

[cfe] Don't find unnamed mixin application in least upper bound

2020-09-09 13:00:17 +00:00

parser_testcases

[parser] Set forIn = true when recovering 'in' written as ':'

2020-09-09 06:41:14 +00:00

test

[cfe] Don't find unnamed mixin application in least upper bound

2020-09-09 13:00:17 +00:00

testcases

[cfe] Don't find unnamed mixin application in least upper bound

2020-09-09 13:00:17 +00:00

tool

[CFE] Change ansi escape code visualization

2020-09-01 13:03:01 +00:00

analysis_options_no_lints.yaml

[cfe] Add predicates to detect late lowered fields.

2020-05-19 08:55:20 +00:00

analysis_options.yaml

…

error_recovery.yaml

…

LICENSE

…

messages.status

[cfe] Report error on nullable spread access

2020-09-09 12:44:37 +00:00

messages.yaml

[cfe] Report error on nullable spread access

2020-09-09 12:44:37 +00:00

PRESUBMIT.py

…

pubspec.yaml

[CFE] Use path-overrides in front_end/pubspec.yaml

2020-08-31 10:52:17 +00:00

README.md

…

testing_with_lints.json

[kernel] Add DartType.toTypeText and Constant.toConstantText

2020-05-18 11:48:20 +00:00

testing.json

[parser] Make begin/end events always come in pairs

2020-09-01 09:30:43 +00:00

README.md

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 [dartanalyzer][analyzercli] command-line tool to analyze their Dart code.

Integrators that want to write tools that analyze Dart code should use the [analyzer] package.

Note: The APIs in this package are in an early state; developers should be careful about depending on this package. In particular, there is no semver contract for release versions of this package. Please depend directly on individual versions.