dart-sdk/pkg/front_end
Johnni Winther 90dd21e5d0 [cfe] Use distinct import uri on patch libraries
This CL changes the import uri of a patch library builder to be its
file uri. This makes patch libraries more like regular libraries,
preparing for full support for patch parts.

Change-Id: I1fa4c10998f17945d6607e1307337b5f66992c3a
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/224947
Commit-Queue: Johnni Winther <johnniwinther@google.com>
Reviewed-by: Jens Johansen <jensj@google.com>
2022-09-29 14:28:57 +00:00
..
benchmarks
lib [cfe] Use distinct import uri on patch libraries 2022-09-29 14:28:57 +00:00
outline_extraction_testcases [CFE] Remove many uses of .packages files in tests 2022-06-22 07:34:49 +00:00
parser_testcases [cfe] Add parser tests for patterns 2022-09-29 09:08:57 +00:00
test [cfe] Add parser tests for patterns 2022-09-29 09:08:57 +00:00
testcases Make internal/patch.part a part of dart:_internal 2022-09-29 11:52:37 +00:00
tool [CFE] Duplicate code finder experiment take #1 2022-09-16 08:56:50 +00:00
analysis_options.yaml
analysis_options_no_lints.yaml [cfe] Add initial support for macro precompilation in incremental compiler 2022-03-09 22:14:05 +00:00
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.json [cfe] Remove language version from inference testcases 2022-07-08 12:52:19 +00:00
testing_with_lints.json

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.