Debugging the player-typed-a-tab problems in Inform 7 for Glulx

[zarf (Andrew Plotkin)]

@zarf

Memory streams should be able to handle arbitrary bytes, yes. I forgot the use case you were going for!

This is obviously complicated by the veneer checking. You can bypass the veneer and use @streamunichar opcodes. But it’s a bit finicky to say “memory streams should be able to handle arbitrary bytes” when printing arbitrary bytes requires hacking around.