fix(bindgen): futures and stream are not Clone
#12155
Open
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.
Discovered this trying to generate bindings for an interface containing something like:
record test { rx: stream<u8>, tx: stream<u8>, }which failed with:
The change is fairly minimal and straightforward, so did not work on a test or anything like that.
I do not like this field name, but splitting into
has_futureandhas_streamwould require splitting also theTypeDefKindmatch cases (which are currently unified) and it did not quite feel right to include this inhas_handleeither.