Files

T

Dmitry Stefantsov e53e5f2475 [cfe] Separate nullability and declared nullability

For some types it makes sense to distinguish between nullability as a
property of including null and the declared nullability, such as for
type-parameter types and FutureOr types.  This CL introduces the
separation between the two concepts.  The plan is to use that when
implementing FutureOrType.

Bug: https://github.com/dart-lang/sdk/issues/40123
Change-Id: I90b45bea768e89c213d021d360a481d38377c682
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/147903
Reviewed-by: Johnni Winther <johnniwinther@google.com>
Commit-Queue: Dmitry Stefantsov <dmitryas@google.com>

2020-05-15 07:38:05 +00:00

benchmarks/ikg

…

lib/src

[cfe] Separate nullability and declared nullability

2020-05-15 07:38:05 +00:00

parser_testcases

Re-apply some recent parser fixes.

2020-05-13 16:00:01 +00:00

test

[cfe] Initial support for external fields.

2020-05-14 18:34:06 +00:00

testcases

[cfe] Initial support for external fields.

2020-05-14 18:34:06 +00:00

tool

[CFE] Error when strong mode mixed with non-opted-in

2020-05-14 17:10:51 +00:00

analysis_options_no_lints.yaml

[cfe] Insert member signatures for nnbd aware inheritance

2020-01-15 07:36:28 +00:00

analysis_options.yaml

…

error_recovery.yaml

…

LICENSE

…

messages.status

[CFE] Error when strong mode mixed with non-opted-in

2020-05-14 17:10:51 +00:00

messages.yaml

[CFE] Error when strong mode mixed with non-opted-in

2020-05-14 17:10:51 +00:00

PRESUBMIT.py

…

pubspec.yaml

Prepare to publish analyzer 0.39.5

2020-04-03 17:28:47 +00:00

README.md

…

testing_with_lints.json

[cfe] Insert member signatures for nnbd aware inheritance

2020-01-15 07:36:28 +00:00

testing.json

[CFE] Error when strong mode mixed with non-opted-in

2020-05-14 17:10:51 +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.