You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The implements rename only happen at the surface level: wrapped-response.request still points to the imported types.request, not wrapped-types.request, which means request cannot be virtualized with just implements.
I can manually duplicate the interfaces and rename them, and not using the implements feature. Just wondering if implements is supposed to work with this kind of virtualization use case. If so, maybe we want to extend the syntax to something like export wrapped-response: response with { types: wrapped-types }.
Another limitation is that we can't write use wrapped-types.{request} in WIT, because wrapped-types is a label, so there is no way to refer to the virtualized wrapped-types.{request} by hand either.
Thanks for filing! Those use cases makes sense. I think both reflect pre-existing limitations in WIT's ability to express arbitrary CM types and implements is just surfacing them more readily. Specifically:
I think your idea for with { types: wrapped-types } mirrors with (modulo syntax) in this comment
We need to be able to write use wrapped-types.{request} for any plain-name wrapped-types (regardless of implements); also highlighted here
Activity
lukewagner commentedon Nov 16, 2026
Thanks for filing! Those use cases makes sense. I think both reflect pre-existing limitations in WIT's ability to express arbitrary CM types and
implementsis just surfacing them more readily. Specifically:with { types: wrapped-types }mirrorswith(modulo syntax) in this commentuse wrapped-types.{request}for any plain-namewrapped-types(regardless ofimplements); also highlighted here