Skip to content

Fix segfault when calling tuple struct constructor as extern fn #8580

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

Closed
wants to merge 2 commits into from
Closed

Fix segfault when calling tuple struct constructor as extern fn #8580

wants to merge 2 commits into from

Conversation

bytwise
Copy link
Contributor

@bytwise bytwise commented Aug 17, 2013

Fixes #5315

@alexcrichton
Copy link
Member

As with #8594, looks good to me, but could you add some extra assertions in the tests that the results of the functions are equal to the structs constructed manually?

Thanks for looking into this!

bors added a commit that referenced this pull request Aug 21, 2013
@bors bors closed this Aug 21, 2013
flip1995 pushed a commit to flip1995/rust that referenced this pull request Mar 24, 2022
Rustup

r? `@ghost`

Nice small sync with only typo fixes

changelog: none
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.

Calling tuple struct constructor as a function causes segfault
3 participants