metal-rs

Thanks very much for this detailed information, it's very helpful. I've filed https://github.com/gfx-rs/metal-rs/issues/222 to track it in the Rust ecosystem side.

Thanks, this is helpful. The specific method that's causing me trouble right at the moment is "computeCommandEncoder"[1], which is a method off MTLCommandBuffer, and I think not in the "new" class. In the Rust bindings[2], this is just a msg_send! and from what I can tell is getting an autoreleased reference, not a retained one. It looks like objc_retainAutoreleasedReturnValue might be exactly what I'm looking for, even if it isn't 100% guaranteed; if I'm understanding, it would be safe, and wouldn't actually leak as long as you had an autorelease pool somewhere in the chain. However, I'm not seeing a binding to it in the objc crate[3]. Sounds like maybe I should file an issue? Also, given that such a method seems obviously useful, I wonder why it's not being called from these C++ bindings? [1]: https://developer.apple.com/documentation/m

> Metal Shaders Write a wrapper, it's easy in Rust. Follow this example https://github.com/gfx-rs/metal-rs > CUDA There's a wrapper. https://docs.rs/cuda/0.1.0/cuda/ > DriverKit There's a wrapper https://github.com/dcuddeback/iokit-sys. > Gtk-rs GTK is terrible, Gtk-rs is putting a lipstick on a pig. I need 2D rendering but also power to touch the gpu to write a shader, to use gl_VertexID when I feel like it. The thing about rust is that that I can legit write my own bindings for any lib written in c/c++, anything else. Like you go from zero to dependency included, building in less than 10sec. The build process is insane. Check out this port of nanovg https://github.com/sunli829/nvg. NanoVG is a popular project with many contributors, this port is a single person project that's better in many ways. With rust you literally just do "git cl