Files

T

Johnni Winther d0b6ce505a [cfe] Handle call tear-off on non-interface types

Closes #54352
Closes #54339

Change-Id: Ia1562a495b97a7a1b0638667b906e805cc12f829
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/341940
Reviewed-by: Chloe Stefantsova <cstefantsova@google.com>
Commit-Queue: Johnni Winther <johnniwinther@google.com>

2023-12-15 12:09:38 +00:00

benchmarks

…

lib/src

[cfe] Handle call tear-off on non-interface types

2023-12-15 12:09:38 +00:00

outline_extraction_testcases

…

parser_testcases

[cfe] Report error on covariant in extension type methods

2023-12-15 09:13:07 +00:00

test

[vm/ffi] Support @Native fields

2023-12-15 11:20:23 +00:00

testcases

[cfe] Handle call tear-off on non-interface types

2023-12-15 12:09:38 +00:00

tool

Migrate dart_doctest_runner.dart to null safety.

2023-12-14 14:29:26 +00:00

analysis_options_no_lints.yaml

[cfe] Add CFE test for DartScope

2023-11-15 10:17:23 +00:00

analysis_options.yaml

…

error_recovery.yaml

…

LICENSE

…

messages.status

[dart:js_interop] Fix checking of type parameters in interop APIs

2023-12-11 21:03:01 +00:00

messages.yaml

[vm/ffi] Support @Native fields

2023-12-15 11:20:23 +00:00

OWNERS

Also add global owners to CFE/VM packages

2023-11-27 14:35:52 +00:00

PRESUBMIT.py

[build] Python 3.12 compatibility.

2023-12-12 18:19:35 +00:00

pubspec.yaml

Enable private field promotion in pkg/front_end

2023-09-18 15:39:47 +00:00

README.md

Fix links in front_end readme

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

testing_with_lints.json

Fix incorrect file reference in license headers

2023-09-18 06:44:08 +00:00

testing.json

[cleanup] Remove references to _2 tests from pkg/front_end

2023-11-27 09:10:34 +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.