Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Properly encode/decode structural variants. #9064

Closed

Conversation

SiegeLord
Copy link
Contributor

Fixes issues #5557 and #8746.

This patch adds an additional family for struct-like variants, and encodes some struct-like aspects of such variants that can then be properly decoded by resolve.

Note that I am not 100% sure how this fix works, but it fixes the issue without breaking any of the tests on my machine.

@luqmana
Copy link
Member

luqmana commented Sep 9, 2013

Should add tests for this.

@huonw
Copy link
Member

huonw commented Sep 11, 2013

The windows test runner (check-fast) doesn't work with aux-build, so you should write something like

// xfail-fast - check-fast doesn't understand aux-build

(At least, that's what a lot of the other aux-build tests have.)

@SiegeLord
Copy link
Contributor Author

Thanks, I wasn't aware of that differences in the test runner itself and thought the xfail-fast was due to compiler limitations.

@luqmana
Copy link
Member

luqmana commented Sep 11, 2013

Well, not really a compiler limitation but more so to do with how check-fast works. Thanks for updating this!

bors added a commit that referenced this pull request Sep 11, 2013
Fixes issues #5557 and #8746.

This patch adds an additional family for struct-like variants, and encodes some struct-like aspects of such variants that can then be properly decoded by resolve.

Note that I am not 100% sure how this fix works, but it fixes the issue without breaking any of the tests on my machine.
@bors bors closed this Sep 11, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants