Results 92 issues of Liam Appelbe

The main design goal is that the script should be composable. It should be easy for the user to integrate the new build stuff with their existing build script if...

package:ffigen

FFIgen and objective_c are pretty tightly coupled. It might make sense to code gen a comment or assert about the version of package:objective_c that the generated code expects. ```dart //...

package:ffigen

Migrate the readme from yaml config to Dart API. In particular, make sure that everything in the large table of yaml options is mentioned in the Dart API docs. Then...

package:ffigen

The new extension types/methods approach in ffigen 20 is not compatible with mocking using mockito. ### Why we switched to extension types - small performance benefit - fewer references from...

package:ffigen

It only has an effect on codegen for functions and globals, and it doesn't really make sense for interfaces/protocols/categories. For interfaces and protocols we could expose the native class/protocol pointer,...

package:ffigen

We have a visitor that tries to decide which imports are needed. Ideally there would be no false positive imports, but that's very hard to guarantee after https://github.com/dart-lang/native/pull/2525.

package:ffigen

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...

package:ffigen

Tests run under `test_with_coverage` can't seem to locate their native assets. This will become more of an issue when Dart 3.10 hits stable and people start using native assets in...

package:coverage