If you're doing graphics then you will have to use `unsafe` to interface with the OS primitives, there's no other way. Backlinks would be "nice" but they break

If you're doing graphics then you will have to use `unsafe` to interface with the OS primitives, there's no other way. Backlinks would be "nice" but they break fundamental assumptions that the borrow checker does. > Detecting a double borrow is the same problem as detecting a double lock of a mutex by one thread, which is being worked on. Is it being worked on using heuristics or formal methods?