Skip to content

Fix tuple instances for IterBytes to avoid ICE, fixes #4092 #4095

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

Merged
merged 3 commits into from
Dec 5, 2012

Conversation

rntz
Copy link
Contributor

@rntz rntz commented Dec 2, 2012

The pattern let &(ref a, ref b) = &selfcauses a compiler ICE. Avoid use of it in libcore/to_bytes.rs.

@rntz
Copy link
Contributor Author

rntz commented Dec 2, 2012

Would fix #4092.

@rntz
Copy link
Contributor Author

rntz commented Dec 3, 2012

Interesting. I can easily fix this, but the behavior you mention also doesn't occur in eg. the IterBytes instance for &[A]. Is that a bug?

This means we will exit early if requested based on the return value of the
callback we're given.
@brson brson merged commit 5b6c1a2 into rust-lang:incoming Dec 5, 2012
@brson
Copy link
Contributor

brson commented Dec 5, 2012

Merged. Thanks.

RalfJung pushed a commit to RalfJung/rust that referenced this pull request Dec 21, 2024
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.

2 participants