Files

T

Paul Berry c509ad1e41 Change "could not" to "couldn't" in error messages

See comments at
https://dart-review.googlesource.com/c/sdk/+/186320/4/pkg/analyzer/lib/src/generated/resolver.dart#3423.
On the recommendation of the documentation team, we use a more
informal tone in messages.

Change-Id: I0c243669ebd91b8f4a745530582e0f829769a754
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/189100
Reviewed-by: Johnni Winther <johnniwinther@google.com>
Commit-Queue: Paul Berry <paulberry@google.com>

2021-03-10 15:26:38 +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

Change "could not" to "couldn't" in error messages

2021-03-10 15:26:38 +00:00

parser_testcases

[parser] Non-crashing recovery of in-progress generification of typedef

2021-02-04 08:01:07 +00:00

test

[kernel] Migrate package:kernel/text_serializer.dart

2021-03-10 13:26:58 +00:00

testcases

Change "could not" to "couldn't" in error messages

2021-03-10 15:26:38 +00:00

tool

[cfe] Actually have both ansi and plain text formatted messages (2nd try)

2021-02-26 13:06:17 +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

[CFE] Enable 'unrelated_type_equality_checks' lint

2020-10-02 11:22:27 +00:00

error_recovery.yaml

…

LICENSE

…

messages.status

[cfe] Add resolution for other member kinds for extension types

2021-03-09 12:49:40 +00:00

messages.yaml

Change "could not" to "couldn't" in error messages

2021-03-10 15:26:38 +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

[kernel] Migrate package:kernel/text_serializer.dart

2021-03-10 13:26:58 +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.