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.

Sign up for GitHub

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

Jump to bottom

Using a different Header representation can lead to an illegal transmute #35

Closed
seanmonstar opened this issue Sep 13, 2014 · 1 comment · Fixed by #36
Closed

Using a different Header representation can lead to an illegal transmute #35

seanmonstar opened this issue Sep 13, 2014 · 1 comment · Fixed by #36
Labels
C-bug Category: bug. Something is wrong. This is bad!

Comments

@seanmonstar
Copy link
Member

No description provided.

@seanmonstar seanmonstar added the C-bug Category: bug. Something is wrong. This is bad! label Sep 13, 2014
@reem
Copy link
Contributor

reem commented Sep 14, 2014

The only way around this is to either store the raw representation or store only a single representation and to keep track of what type was used to generate that representation.

@seanmonstar seanmonstar mentioned this issue Sep 14, 2014
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
C-bug Category: bug. Something is wrong. This is bad!
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

adjust representation of internal Items hyperium/hyper
2 participants
@seanmonstar @reem