Host extension compatibility matrix

[Alloyed]

given that clap is stongly extension based i think it'd be neat to have a direct caniuse-style resource for what you can/can't expect from hosts. and then in reverse, if a host implements an extension, does that improve compatibility with existing plugins?

This is kind of inspired by me following the nakst tutorial, only to find out that it uses as part of its windows gui implementation an extension that doesn't seem to be supported on bitwig windows! (timer-support) better to know than not, i suppose

https://alloyed.notion.site/20b91eb37775804d9c89f1ce428d64cc?v=20b91eb377758070919d000cb1babba0

i wonder if there's an easy equivalent to find out which plugin extensions will actually get used by a given host, too. the best i can think of is make a plugin that tracks every call to get_extension? but it seems perfectly reasonable on the host side to stop querying for extensions if it depends on an extension that i return false for....

[baconpaul]

this is partly the idea of the nascent, incomplete, messy validator plugin which is a plugin which can probe a host.

https://github.com/free-audio/clap-validator-plugin

radically incomplete effort