> BTW what's the story with enforcing alignment restrictions. It's > not the case that the C types char* and int* are semanticlly the > same because of potential alignement constraints, but the MLton FFI > maps them to the same Pointer.t which I think is wrong. Can you explain how this prevents writing a certain program or causes other problems?