Files

T

Devon Carew c49cfa690d Replace crc32 with fletcher16 for a faster checksum algorithm.

Change-Id: I200e8450eb4a27e1c8093f400f8fe5f864f4c026
Reviewed-on: https://dart-review.googlesource.com/65444
Commit-Queue: Devon Carew <devoncarew@google.com>
Reviewed-by: Paul Berry <paulberry@google.com>
Reviewed-by: Konstantin Shcheglov <scheglov@google.com>

2018-07-18 03:30:44 +00:00

benchmarks/ikg

Smaller changes to incremental_perf.dart, this is preparation for the flutter IKG perf benchmark

2017-11-17 10:34:12 +00:00

lib/src

Replace crc32 with fletcher16 for a faster checksum algorithm.

2018-07-18 03:30:44 +00:00

test

Replace crc32 with fletcher16 for a faster checksum algorithm.

2018-07-18 03:30:44 +00:00

testcases

Store resolution for using non-constant factory for constant instance creation.

2018-07-17 17:34:12 +00:00

tool

Add more error message mappings

2018-07-09 16:38:08 +00:00

analysis_options.yaml

Update analysis options files.

2018-07-03 00:20:06 +00:00

error_recovery.yaml

…

LICENSE

…

messages.status

Use InvalidUseOfNullAwareAccess and ThisOrSuperAccessInFieldInitializer rather than Unspecified

2018-07-18 01:00:51 +00:00

messages.yaml

Use InvalidUseOfNullAwareAccess and ThisOrSuperAccessInFieldInitializer rather than Unspecified

2018-07-18 01:00:51 +00:00

pubspec.yaml

Prep for analyzer 0.32.3, front_end 0.1.3, kernel 0.3.3

2018-07-04 04:30:09 +00:00

README.md

Prepare for analyzer 0.32.0.

2018-05-14 18:07:02 +00:00

testing.json

[VM] Turn dart2 on by default on the command line VM

2018-06-18 22:31:32 +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 [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.

Note: The APIs in this package are in an early state; developers should be careful about depending on this package. In particular, there is no semver contract for release versions of this package. Please depend directly on individual versions.