native
native copied to clipboard
dart-lang
Dart packages related to FFI and native assets bundling.
The record-use experiment is currently only available in Dart standalone. We need to add an experiment flag to Flutter to enable it there.
@mosuem added `class RecordUse` to `package:meta`, should we consider moving it to `package:record_use`? Pros: * Discoverability: The input and output live in the same package. * (Single dependency for both...
The current JSON structure for `package:record_use` only supports string keys for `MapConstant` objects. The keys are serialized directly as strings, while the values are normalized as indices into the `constants`...
Currently, the recording mechanism only captures statically-resolved calls (`StaticInvocation`) and tear-offs (`StaticTearOffConstant`). It does not record truly dynamic calls, such as `foo.bar()` where `foo` is a `dynamic` variable. We should...
We might have use cases where 1. we generate a data asset (yaml/json) from Dart code with annotations in a generate or build hook, and 2. tree-shake such data asset...
We should prototype and implement the protobuf aware tree-shaker on top of `@RecordUse` annotations if we can. 1. Prototype, see if it's possible. 2. Implement fully. Sources: * https://github.com/dart-lang/sdk/blob/37f468c93638ecabe8a1bd4b488785cccf597ea7/pkg/vm/bin/protobuf_aware_treeshaker.dart#L119
We should prototype and implement the Flutter icon tree shaker with `package:record_use`. 1. Prototype to prove out that that it works. 2. And, then figure out what we need to...
The current API for retrieving recorded method calls is convenience-oriented, providing methods like `constArgumentsFor()` and `hasNonConstArguments()`. This leads users to forget to call `hasNonConstArguments`. **Proposed Solution:** Refactor the API to...
ObjC implementation of jnigen's [context proposal for interface implementation](https://github.com/dart-lang/native/issues/575#issuecomment-2650984617). The idea is that this context map would be stored on the native side as a map of weak references, to...
And follow Google C++ Style in the code.
