Halil Durmus
1a8afa6bbf
This change simplifies working with `@Native`-annotated functions by allowing the native type to be omitted when it can be inferred from the Dart function's signature. While this was previously supported for `@Native` fields, it now applies to functions as well. Before this change, you needed to specify the native type explicitly: ``` @Native<Void Function(Pointer)>() external void free(Pointer p); ``` After this change, the native type can now be omitted if it's clear from the Dart signature: ``` @Native() external void free(Pointer p); ``` TEST=tests/ffi/native_assets/* CoreLibraryReviewExempt: VM only Closes: https://github.com/dart-lang/sdk/issues/54810 Change-Id: Ied5407fcd2f49d85284cb7817f0c8cad2a73626b Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/400840 Reviewed-by: Daco Harkes <dacoharkes@google.com> Commit-Queue: Daco Harkes <dacoharkes@google.com> Reviewed-by: Johnni Winther <johnniwinther@google.com> Reviewed-by: Moritz Sümmermann <mosum@google.com> Reviewed-by: Brian Wilkerson <brianwilkerson@google.com>
FE/analyzer shared code
This package contains logic that is shared between the front_end and analyzer packages. It is intended solely to facilitate development of the Dart SDK, and is not intended for use by end users. In particular, this package has no public API, so no guarantee is made of compatibility between one version of the package and the next.
End users should consider using the analyzer package to analyze Dart source code.