Wow what a neat project, I have spent a lot of time recently working around vulkan on m1 machines with compatibility layers and while it’s not a huge pain it does suck to miss out on some of the more powerful features of vulkan that the hardware is certainly capable of. I’m not keen on learning metal to bridge the gap and this is just what the doctor ordered.
This will be a huge boon for me, way to go!
We don’t deserve our open source heroes, so grateful for the incredible free software ecosystem
Gimp, 7zip, blender, vlc, open office, the kernel, thousands of others, I feel like our lives have been universally improved by these inverted charity projects. The few taking care of the undeserving many.
Rocket chat I think checks those boxes
Ngl kaspersky is the close to the last group I care to hear from about security
Aww man uncalled destructors were definitely not even on my radar
The real example of a health check trait really brings this issue to life, it’s linked within op’s article as well
Is this a reasonable summary?
Say you want a trait where a method returns a task that you would like to sometimes run within your own thread and sometimes move it to a separate thread to be executed, that means the Send constraint isn’t necessary to add to your trait but it would be nice to add that constraint within another method’s parameter definition so that it can accept structs that implement the trait and further constrain that implementation to be Send’able. That’s now possible with this new rust language feature, though it was previously possible through a crate, now it’s no longer needed.