Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@nevkontakte
Copy link
Member

@nevkontakte nevkontakte commented Apr 19, 2022

When a function literal is used that calls another function and that other function has yet to be analyzed, the call site for the function literal is not retained, so it's not processed later, so the function that was calling the function literal is not made blocking itself, when it should be.

This change makes blocking status propagate through any number of intermediate literal function calls.

This is a rebase of #956 with additional regression tests.

Fixes #955.

When a function literal is used that calls another function and
that other function has yet to be analyzed, the call site for
the function literal is not retained, so it's not processed later,
so the function that was calling the function literal is not made
blocking itself, when it should be.

This change makes blocking status propagate through any number of
intermediate literal function calls.

This is a rebase of gopherjs#956.

Fixes gopherjs#955.

Co-authored-by: Frank Rehwinkel <[email protected]>
@nevkontakte nevkontakte merged commit 3f8f90c into gopherjs:master Apr 19, 2022
@nevkontakte nevkontakte deleted the issue955 branch April 19, 2022 14:28
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.

compiler/analysis/info.go function literal call site not recorded for later marking

2 participants