> > So, given all that, is there any way to add the "target-specific > > size_t" portion without waiting for-who-knows-how-long for the intN_t > > and enum-size-type projects to finish? Some form of interim API that > > we can put in, so that we can start working on finding all the > > assumptions about size_t, while waiting for the rest to finish? > > I have no idea how ugly something supporting target-specific strings would > be, since supporting such strings for these standard typedefs never seemed > to be a direction we wanted to go in.
I tried to hack in support for intN_t in a backend, and it was a maze of initialization sequence nightmares. So I guess we need to do the intN_t part first. Is someone working on this? If not, is there a spec I could use to get started on it?
