Files

T

Dmitry Stefantsov 11790fe024 [cfe] Warn about non-nullable operands in null-aware operations

Closes #40094.

Bug: http://dartbug.com/40094
Change-Id: I3af5258bf0845257915eb090889fde0fdcb96bf9
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/134339
Commit-Queue: Dmitry Stefantsov <dmitryas@google.com>
Reviewed-by: Johnni Winther <johnniwinther@google.com>

2020-02-06 11:06:41 +00:00

benchmarks/ikg

…

lib/src

[cfe] Warn about non-nullable operands in null-aware operations

2020-02-06 11:06:41 +00:00

parser_testcases

[CFE] Parser test for class called late and required

2020-02-04 13:45:31 +00:00

test

[cfe] Warn about non-nullable operands in null-aware operations

2020-02-06 11:06:41 +00:00

testcases

[cfe] Warn about non-nullable operands in null-aware operations

2020-02-06 11:06:41 +00:00

tool

[cfe] Remove use of '--strong'

2020-01-17 17:44:45 +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

[CFE] First batch of fixes for requiring explicit types

2019-08-15 13:13:20 +00:00

error_recovery.yaml

…

LICENSE

…

messages.status

[cfe] Warn about non-nullable operands in null-aware operations

2020-02-06 11:06:41 +00:00

messages.yaml

[cfe] Warn about non-nullable operands in null-aware operations

2020-02-06 11:06:41 +00:00

PRESUBMIT.py

[CFE] Add PRESUBMIT.py that runs a little smoke testing

2019-08-16 12:28:07 +00:00

pubspec.yaml

[CFE] Proof of concept of using vm service to find leaks

2020-01-23 08:30:07 +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] Check class hierarchy in incremental compiler test

2020-01-31 10:38:41 +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.