Skip to content

Conversation

@stevenfontanella
Copy link
Member

Reverts #8115

This causes the fuzzer to fail when an import is repeated: #8115 (comment). Will revert and re-introduce this later with a fix.

@kripken
Copy link
Member

kripken commented Dec 16, 2025

We don't need to quickly revert this - but up to you.

If you have time to find a fix today, that seems fine to me. If it would wait several days, then a revert would make more sense to me.

@stevenfontanella
Copy link
Member Author

Got it, it should be an easy fix. Let me give it a try

@stevenfontanella stevenfontanella marked this pull request as draft December 16, 2025 17:35
@stevenfontanella stevenfontanella marked this pull request as ready for review December 17, 2025 01:59
@stevenfontanella
Copy link
Member Author

I wasn't able to get to the fix today. We can go ahead and merge this and I'll roll forward later.

@stevenfontanella stevenfontanella enabled auto-merge (squash) December 17, 2025 02:01
Copy link
Member

@tlively tlively left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The fix turns out to be trickier than expected because imports with the same name may have incompatible types. JS can make instantiation succeed even in these cases, so we need to figure out how to make instantiation succeed when we interpret modules with such imports as well.

@stevenfontanella stevenfontanella merged commit 986e7cb into main Dec 17, 2025
18 checks passed
@stevenfontanella stevenfontanella deleted the revert-8115-ctor-import branch December 17, 2025 02:03
@stevenfontanella stevenfontanella linked an issue Dec 18, 2025 that may be closed by this pull request
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.

ctor-eval crashes when the same name is imported twice

4 participants