[ffigen] feat: generate cpp class constructor bindings

[Hassnaa9]

No description provided.

[github-actions]

Package publishing

Package	Version	Status	Publish tag (post-merge)
package:code_assets	1.2.0	already published at pub.dev
package:data_assets	0.20.0	already published at pub.dev
package:ffi	2.2.0	already published at pub.dev
package:hooks	2.0.0	already published at pub.dev
package:hooks_runner	1.4.0	already published at pub.dev
package:jni_flutter	1.0.1	already published at pub.dev
package:native_toolchain_c	0.19.1	already published at pub.dev
package:record_use	0.6.1-wip	WIP (no publish necessary)
package:swift2objc	0.2.0	already published at pub.dev
package:swiftgen	0.1.3	ready to publish	swiftgen-v0.1.3

Documentation at https://github.com/dart-lang/ecosystem/wiki/Publishing-automation.

[github-actions]

PR Health

Breaking changes ✔️

Package	Change	Current Version	New Version	Needed Version	Looking good?

This check can be disabled by tagging the PR with skip-breaking-check.

API leaks ✔️

The following packages contain symbols visible in the public API, but not exported by the library. Export these symbols or remove them from your publicly visible API.

Package	Leaked API symbol	Leaking sources

This check can be disabled by tagging the PR with skip-leaking-check.

Changelog Entry ✔️

Package	Changed Files

Changes to files need to be accounted for in their respective changelogs.

This check can be disabled by tagging the PR with skip-changelog-check.

[liamappelbe]

Can you use the existing Scope and Symbol infra for this? Change CppMethod.name to a Symbol, wire it up in the visitors etc, and set the base name of all the constructors to the glueName below (without the suffix, so I guess ${name}_new?)

[liamappelbe]

Constructing LocalVariables inline like this means you're never actually writing the local variables it creates. I think once you start dealing with memory management stuff, you'll need to deal with LocalVariables properly, since safely unwrapping a pointer from a NativeFinalizer requires creating a temporary local variable.

Take a look at how other bindings generators deal with LocalVariables. You'll basically need to create one LocalVariables instance per method, do all your conversions (but don't write them to your bindings yet), then call LocalVariables.generateDeclarations() and write the string to your bindings, then write the conversion strings. Basically, the local variable declarations need to be written to the bindings before the conversions that use those local variables.

Example of writing LocalVariables to the bindings. Example showing how LocalVariables are being used for pointer unwrapping (you'll need to do this sort of thing when you start doing memory management). This bug and this one explain why this unwrapping step is needed, if you want to read more about it.

[Hassnaa9]

Ok, I have tried to follow the links you mentioned; let me know if there are any other enhancements