overrides in packages

[mighdoll]

We want packages to be able to write overrides in some form.

But packages aren't in a good position to choose unique application wide names for overrides or to decide which overrides are needed for a particular application.

Instead, the application wesl should select which imported package overrides to expose to the host as part of the application, and have the ability to rename package overrides. A package that imports other packages should have similar controls.

Should application packages write override or use some other syntax? How should application wesl and package wesl select and optionally rename the overrides from imported packages?

[mighdoll]

Similarly to #41, what happens to package overrides that are not selected by the app wesl? What if package overrides are not selected by the app wesl, but are indirectly referenced by a package function that is imported by the app wesl?

I'd suggest:

• package overrides that are not selected by the app wesl and are not referenced indirectly by a function that is imported by the app wesl should be removed, not included in the output wgsl generated by the linker
• package overrides that are only indirectly referenced by the app wesl should be converted to const and included in the linked result