mirror of
https://github.com/dart-lang/sdk
synced 2024-11-02 12:24:24 +00:00
709c1e0b75
In kernel, library import URIs now support an "app" scheme as an alternative to the "file" scheme, representing a path relative to the application root. dartk takes an --app-root flag giving the application root. If none is given, file URIs are used instead. The intention is that kernel binaries should not carry irrelevant path information, such as the path to the home directory of the user who compiled a given file. It is not the intention that end-users should see an app URI. Import paths are currently not shown to users at all, and if we need to do this, they should be translated to file paths first. In theory we could stick to file URIs with relative paths, but the Uri class from dart:core makes this difficult, as certain operations on it assume that file paths should be absolute. Source mapping URIs are not yet affected by this change. R=kmillikin@google.com Committed: |
||
|---|---|---|
| .. | ||
| lib | ||
| test | ||
| tool | ||
| .analysis_options | ||
| BUILD.gn | ||
| LICENSE | ||
| pubspec.yaml | ||
| 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.