Announcing the Android Workgroup

[Finagolfin]

@Max_Desiatov

This is incorrect. Embedded Swift SDK for Wasm does rely on WASI and does include and link WASI-libc. If users don't adopt any of its APIs, those dependencies will be eliminated with optimizations, but they are there when needed.

I have never used WASM or the new Embedded Swift mode, so only had a hazy notion of precisely what they invoked: thanks for the correction.

@Max_Desiatov

The main gain of Embedded Swift is that with forced specialization of generics and additional restrictions the dependency on major parts of Swift runtime is eliminated. In a lot of cases this allows creating binaries that only take only tens or hundreds of kilobytes. I can't speak for all Android users and developers, but I would anticipate some of them to be interested in this. Whether the trade-off is worth it is another question.

OK, good to know.

@Max_Desiatov

In my experience, this only reduces the final binary by a few megabytes, but not enough when there's a need for it to be much smaller.

On which platform? On non-Darwin platforms, FoundationInternationalization ships with its own copy of ICU, including a large icudata array with info for a lot of timezones and languages. Our tests show almost 30 MB saved when not using it, surprised you're seeing anything different.