Srujan Gaddam
8c62ad7596
This revisits the validation after the redesign. The changes from before the redesign include: - Accounting for multiple extensions on @staticInterop classes - Users can implement any of the extension members for a given export name, with the exception that if there is a getter/setter pair, both should be implemented if any one of them are - Since this validation goes on top of exports, the Dart class needs not be processed, and we use the same export creation process to create the mock Change-Id: I05a7cff765d6d37d3955dd93676e2d55d2b201b3 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/262862 Reviewed-by: Riley Porter <rileyporter@google.com> Reviewed-by: Sigmund Cherem <sigmund@google.com>
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.