Hello android developers,
As the android support matures, many things which initially made sense or were done for expediency start to stick out as problem areas. One area that I would like to address is the system libc inclusion. Currently, the system libc on android is imported as
glibc as the module name is
swiftGlibc. However, android's libc implementation is bionic, which is not particularly compatible with glibc, and has sufficient differences that the module map for the library is even split out.
I think that things are now in a place where it would be possible to rename the module from
bionic. The one problem that crops up is that this would be a source compatibility break on android. Fortunately (or unfortunately?) we do not have any stability guarantees on non-Darwin platforms.
For those that think that android would be the odd platform in this case, I will point out that Windows uses
ucrt for the module name as per the name of the system libc.
The question that comes up though, are there packages that we could not update for this and thus we need to provide some sort of staging or if we can just break compatibility with the next major release? That is where the input of other android folks would be useful.