sjindel-google

AOT is done, only the ARM64/IA32 support is missing.

Note that the exactness checking in the IC stubs is only implemented on x64.

It sounds like variadic functions are supported as well as possible, given that Dart does not have variadic functions (except for `noSuchMethod`).

> > given that Dart does not have variadic functions > > We _could_ support variadic functions with a List as argument in the Dart signature, if we really wanted...

+1

I've identified how all four use cases can be solved within the existing Gradle/Cocoa Pods systems for Flutter on Android, iOS and MacOS. Both systems have first-class support for "native"...

/cc @jonahwilliams @mit-mit

@hanabi1224 `DynamicLibrary.process` is here to stay and will be included whenever Flutter ships their next release. I believe it's already available on their dev channel.

I've added a walkthrough to the wiki page: https://github.com/flutter/flutter/wiki/Binding-to-native-code-via-FFI This illustrates how to add the C/C++ sources directly so they will be compiled for the correct architecture for the end...

I would also like to have a different template for an FFI-based package, but the plugin system actually provides a lot of useful plumbing besides method channels. 1. Including "native"...