How to handle size_t in front ends?

When reading this thread it occured to me that
one could reserve i0 as an integer type that
is semantically identical to iN where N is
the size of (i8*) in bits.

But on the other hand I just woke up, so this
might be a silly idea :slight_smile:



The word opaque comes to mind. The basic question is, do you want people to be able to understand this stuff, or is it more like the bitcode file, you don't care that it is unreadable?