Vulkan Descriptor Update Extensions Wired Up For Intel's ANV Driver

[phoronix]

Phoronix: Vulkan Descriptor Update Extensions Wired Up For Intel's ANV Driver

Intel's ANV Vulkan driver in Mesa Git has picked up support for two more extensions of this week's big Vulkan update...

http://www.phoronix.com/scan.php?page=news_item&px=Vulkan-Descriptor-ANV-Lands

[FireBurn]

Seems like a no brainer, if apps are looking to use these new extensions then mesa should support them and help iron out the bugs for them. If they aren't ratified or used they can be removed and when they're promoted to non-X extensions the can be renamed and or aliased

[nanonyme]

Apps to actually use experimental extensions sounds like a horrifyingly bad idea to me. The experimental name can then effectively never be changed without breaking apps that test for its existence

[nanonyme]

Also the final form might even end up functionally different so you'd effectively end up supporting two implementations forever

[plonoma]

whether to land the "KHX" experimental extensions into mainline Mesa Git or keep them in a branch until they've been declared stable.

Having application developer feedback is a very useful thing, necessary even for improving the extensions.
I would suggest the following:
Put the experimental extensions behind a per app command line switch.
An sort of 'enableExperimentalExtensionsKHX' argument.
Don't allow the command line switch to be on for the driver in general.
Only allow per-binary/executable/application arguments.
Thus apps need to be launched with this command line argument if they want to use the experimental extensions.
Experimental means experimental, not stable. Application developers should expect experimental stuff to change and break sometimes.
There is also nothing wrong with popping up a dialogue box saying any driver update can change any experimental extension behaviour without any prior notice and make your application crash, not working, unusable.