Moritz

The API is starting to look a bit overloaded with arguments. I wonder if there is a way to simplify this. Maybe use asset types instead? This would make asset...

> For bundled data assets that are used as bytes/strings in Dart code, we should be able to both support hot restart and hot reload. Does is make sense to...

Comment on testing hooks: This might introduce more dependencies, such as `package:test`, but there is no real way around this. Extracting testing into a separate package doesn't help, as anyone...

As discussed earlier: In would be even nicer if adding all assets was enabled by default. This requires us to land automatic treeshaking of assets first, and needs special care...

Option2, but in it's own package. I would try to keep things simple, and have a new asset type for the `PrivacyManifestAsset` defined in `package:privacy_manifest_asset`, which also exposes helper methods...

Throwing some nice not-as-technical names in the ring: `package:weave` or `package:forge` (my personal favorite).

> Should we consider `package:data_asset` and `package:code_asset` instead? Yes (let the bike shedding stop 😉 ). I am also fine with `package:hooks` though. We should just be kind of consistent.

Static linking will not be supported in the foreseeable future, but we are planning on producing a static library to remove unused symbols with the linker in the link hook,...

@knopp - just curious, any changes in `native_toolchain_rust` so far to accomodate this use case? https://github.com/dart-lang/i18n/pull/866 adds even more rust stuff... :)

Thanks - let me take a look. > No support for static libraries, but I think I'd wait with that until there is actual support in native assets. #866 will...