fix(provider-wit-bindgen): type aliasing for nested types #1618
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Feature or Problem
When using a type alias in WIT (ex.
type str-list = vec<string>
), if that type is inside an interface and used from another interface, there is an extra alias made to it.Since bindgen sees both the "real" alias (in Rust
type StrList = Vec<String>
) and the local binding level alias (in Rusttype StrList = super::some::iface::StrList
), we need to make sure that the "real" alias is the one that is hoisted to the top.This commit adds some checks to ensure that the alias that is not a reference is sure to be hoisted to the top (all generated code uses
T
, notsuper::some::iface::T
). This is a a shortcut to avoid building a type reference graph.Related Issues
Release Information
Consumer Impact
Testing
Unit Test(s)
Acceptance or Integration
Manual Verification