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>
analysis_server
A long-running process that provides analysis results to other tools.
The analysis server is designed to provide on-going analysis of one or more code bases as those code bases are changing.
Using the server
The analysis server is not intended to be used stand-alone, and therefore does not have a human-friendly user interface.
Clients (typically tools, such as an editor) are expected to run the analysis
server in a separate process and communicate with it using a JSON protocol. The
original protocol is specified in the file analysis_server/doc/api.html
and Language Server Protocol support is documented in
tool/lsp_spec/README.md.
Features and bugs
Please file feature requests and bugs at the issue tracker.