Fix address of function in decltype context #202
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There is a check that tries to prevent you from taking the address of a wasm function from genericjs, or vice versa. The check uses
CurScope->getFnParent()
to get the function in which the address of operator takes place. This is not a reliable way to get the current function declaration, and its usage here allows some invalid code to sneak past the check.getCurFunctionDecl()
is a more reliable way to get the current function declaration, and using it, the above code no longer compiles (yay!).There is one place in
cheerp/client.h
where the address of a wasm function is taken from inside a decltype expression in the return type of a genericjs function. Because the operand of a decltype expression is never evaluated, we can always allow taking the address of a function like this as long as it happens in a decltype expression. And, this way, there is no issue incheerp/client.h
.