Daniel Keller

Thanks for the explanation! What about something like RAII objects? This seems to be the pattern the standard library uses to run tear-down code, for example unlocking mutexes.

I do this the other way around: I have wrappers for vk::Device, vk::Instance, etc that destroy them when they're dropped. That way I can use the regular drop order rules...

I get incorrect output for `&&str` as well.

I had a similar idea of an "hx-local" or "hx-template" attribute: it acts like hx-get, except instead of a url it takes an element reference, and the "ajax response" instead...

The code to do this is pretty straightforward. I don't have an actual patch, but you can see my implementation in the first few files of [this diff](https://github.com/danielkeller/Violet/commit/e3ff39ff726fe1f594fc3f08848fcbcdc4a5bee2).