I went back to Cohost today to try and finish up the device refactor, and got pretty close. The last piece that I'm stuck on now is how to assign vectors to a device. One of the points of this approach is that devices can be plugged in dynamically, but routines are also supposed to be dynamic and yet have a static implementation; perhaps there should be a "static" starting point to help things make sense. Uxn uses the idea of a device page, where you actually have to "program" your devices in your source code by writing out to them and telling them what their vectors are. This might be a good approach; I have plenty of opcodes to spare, and it would enable more dynamic self configuration later on.

So I should just add an opcode for setting the vector at a slot index? Seems easy enough.

---

The vector setting opcode worked really well, and now I need to clean up all of the messes I've made in the host.rs and device.rs files. Data is almost flowing all the way through in both directions, and I think some refactoring would make a big difference in simplicity and reliability.