Files

T

Johnni Winther 3e6050a158 [cfe] Handle structurally constant record literals

Closes #50022

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

2022-09-21 14:19:16 +00:00

benchmarks

[CFE] Benchmarks for list copy, mapping etc.

2022-01-24 14:40:26 +00:00

lib

[cfe] Handle structurally constant record literals

2022-09-21 14:19:16 +00:00

outline_extraction_testcases

[CFE] Remove many uses of .packages files in tests

2022-06-22 07:34:49 +00:00

parser_testcases

[parser] Empty record types, record types with 1 element

2022-08-30 11:04:10 +00:00

test

Revert "Reland "[cfe,corelib] Add class 'Record' to the core library""

2022-09-19 13:52:01 +00:00

testcases

[cfe] Handle structurally constant record literals

2022-09-21 14:19:16 +00:00

tool

[CFE] Duplicate code finder experiment take #1

2022-09-16 08:56:50 +00:00

analysis_options_no_lints.yaml

[cfe] Add initial support for macro precompilation in incremental compiler

2022-03-09 22:14:05 +00:00

analysis_options.yaml

…

error_recovery.yaml

…

LICENSE

…

messages.status

[pkg:js] Add type/conformance checking for createStaticInteropMock

2022-09-16 20:13:30 +00:00

messages.yaml

[pkg:js] Add type/conformance checking for createStaticInteropMock

2022-09-16 20:13:30 +00:00

OWNERS

[infra] Add OWNERS to the Dart SDK

2022-02-14 14:06:34 +00:00

PRESUBMIT.py

…

pubspec.yaml

[pkg] prefer 'any' deps for package dev dependencies

2022-05-27 01:34:59 +00:00

README.md

…

testing_with_lints.json

Replace a bunch of references to .packages

2021-10-12 20:16:15 +00:00

testing.json

[cfe] Remove language version from inference testcases

2022-07-08 12:52:19 +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.