Support for @unstable WIT features #110
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@dicej just pinging again in case you missed it. Let me know if there are any changes you'd like to see. If you are just busy, no rush. Thanks! |
|
BTW, I'll do a new 0.15.0 release with this and the other recent changes when I get a chance. |
|
Perfect thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Provides the ability to pass in arguments for enabling
@unstablefeatures in a given WIT world.If passed in, then the correct bindings will be generated, as well as when building the component.
For this to work, the features must be passed into both calls, but that seems reasonable.
The API for the flags was copied straight from the
wit-bindgencli, so it should be identical.Addresses #109