Dzmitry Malyshau

@apricotbucket28 done

This path is no longer viable, since as of #203 we don't have a specific surface any more when creating a GPU context. We'll need to find a better path.

I've recently completed moving Blade to objc2, since it was blocking my blade-graphics-0.6 release. Seems to be working well: there are zero instances of `msg_send!` left in code now! Might...

Oh that's interesting. We assume that the platform-specific side is provided given the base extension support. It's strange that lavapipe doesn't expose it like this. @ewoudje any recommendations?

I think we want is "just also checking the platform specific extensions". @ewoudje would you be kind enough to make this patch?

https://github.com/kvark/blade/pull/259 addresses this issue. I can run "vehicle" with lavapipe locally.

Might be just the check being overly strict. I made it proper in https://github.com/kvark/blade/pull/269

The vehicle example crash is `ERROR_UNKNOWN`, which is driver failing to compile the program internally. It could be a result of the program being invalid, but then the validation layers...

Oh that's such a non-obvious limitation. Good to know it's by design, I can write my code without assuming this will come.

So it hands on 3 different systems, technically? That's definitely unexpected!