Files

T

Jens Johansen 8270944c5d [CFE] Extend weekly test - fuzz tests and advanced invalidation leak test

We currently run our leak tests weekly.
This extends it so we also run leak tests with advanced invalidation,
as well as our strong and weak tests with fuzzing enabled.

Change-Id: I2c941f58594791d1981c6b6612db2205b68f5e19
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/192682
Reviewed-by: Johnni Winther <johnniwinther@google.com>
Commit-Queue: Jens Johansen <jensj@google.com>

2021-03-24 14:44:51 +00:00

benchmarks/ikg

[kernel,front_end] Migrate first wave of pkg/kernel and pkg/front_end

2021-01-18 15:40:21 +00:00

lib

front_end: Remove unnecessary import

2021-03-24 13:30:49 +00:00

parser_testcases

[parser] Test for (already fixed) issue 45327

2021-03-16 14:45:00 +00:00

test

[CFE] Extend weekly test - fuzz tests and advanced invalidation leak test

2021-03-24 14:44:51 +00:00

testcases

[CFE] Crash reproductions

2021-03-24 13:45:31 +00:00

tool

[cfe] Move ExtensionType into pkg/kernel/lib/ast.dart

2021-03-12 19:02:27 +00:00

analysis_options_no_lints.yaml

[cfe] Refactor ClassHierarchyBuilder to use Tuple for computation

2021-01-19 19:52:13 +00:00

analysis_options.yaml

…

error_recovery.yaml

…

LICENSE

…

messages.status

[vm/ffi] Support packed Structs

2021-03-19 15:34:42 +00:00

messages.yaml

[vm/ffi] Support packed Structs

2021-03-19 15:34:42 +00:00

PRESUBMIT.py

…

pubspec.yaml

[kernel,front_end] Migrate first wave of pkg/kernel and pkg/front_end

2021-01-18 15:40:21 +00:00

README.md

Fix links in front_end readme

2020-12-07 15:02:57 +00:00

testing_with_lints.json

…

testing.json

[CFE] Include .crash_dart in weak tests; better handling of erroneous -D parameters and expectationFileMismatchSerialized on -DupdateExpectations=true

2021-03-19 13:34:17 +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 dart analyze command-line tool to analyze their Dart code.

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

Note: A previous version of this package was published on pub.dev. It has now been marked DISCONTINUED as it is not intended for direct consumption, as per the notes above.