Skip to content

Update CG-02-25.md #1765

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
May 8, 2025
Merged

Update CG-02-25.md #1765

merged 3 commits into from
May 8, 2025

Conversation

tlively
Copy link
Member

@tlively tlively commented Feb 25, 2025

No description provided.

@tlively tlively requested a review from dschuff February 25, 2025 18:45
Comment on lines 102 to 104
RH: I think you could still do lazy instantiation. My fear about doing global init is that [... ]

CW: Why is it important that this goes in this way …
Copy link
Member Author

Choose a reason for hiding this comment

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

@eqrion, @conrad-watt, do you remember what you said here?

Copy link
Contributor

Choose a reason for hiding this comment

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

"I think you could still do lazy initialization of globals in the case where none of the global initializers do any calls to imports. My fear about allowing global initializers to call imports is that a global initializer could get a funcref, call an import with that funcref, then have that import call back into the module and observe uninitialized globals"

@dschuff dschuff merged commit 259707a into main May 8, 2025
@dschuff dschuff deleted the tlively-patch-4 branch May 8, 2025 20:48
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.

3 participants