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

Fix issue #3501: Don't re-define struct TypeInfos #3502

Merged
merged 1 commit into from
Jul 10, 2020

Conversation

kinke
Copy link
Member

@kinke kinke commented Jul 10, 2020

Surfacing now as #3486 added a corresponding assertion.

I've tested this with an older vibe-d v0.8.6 lying around on my box.
The assertion was hit for the TypeInfo of a nested struct:

https://github.com/vibe-d/vibe.d/blob/3c7ae13989003b7ebc59de23c5b6a0fb0466f119/http/vibe/http/router.d#L570-L574

I wasn't able to quickly reduce it to a stand-alone testcase and am reluctant to put any more effort into this.

Surfacing now as ldc-developers#3486 added a corresponding assertion.

I've tested this with an older vibe-d v0.8.6 lying around on my box.
The assertion was hit for the TypeInfo of a nested struct:

https://github.com/vibe-d/vibe.d/blob/3c7ae13989003b7ebc59de23c5b6a0fb0466f119/http/vibe/http/router.d#L570-L574

I wasn't able to quickly reduce it to a stand-alone testcase and am
reluctant to put any more effort into this.
@kinke
Copy link
Member Author

kinke commented Jul 10, 2020

I've just verified that the issue would be fixed by #3491 as well.

@kinke kinke merged commit e6a2dd8 into ldc-developers:master Jul 10, 2020
@kinke kinke deleted the fix3501 branch July 10, 2020 21:31
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.

1 participant