Do not return a no-op function if default function isn't found#1927
Do not return a no-op function if default function isn't found#1927AlexEne wants to merge 1 commit into
Conversation
|
It seems I have missed some tests, right now the following are failing: |
Subscribe to Label Actioncc @peterhuene DetailsThis issue or pull request has been labeled: "wasmtime:api"Thus the following users have been cc'd because of the following labels:
To subscribe or unsubscribe from this label, edit the |
|
Maybe @alexcrichton? |
|
I've requested review from @sunfishcode for this |
|
@sunfishcode if you're ok with this change I'll go ahead and fix the tests. |
|
This change looks good to me. This is a space that we're still figuring out as we go; I think making it an error now makes sense. |
|
Ok, I'll fix the tests and update this PR in the next days |
|
Oh wow, I forgot about this. So sorry. I would be able to pick it up again later next week, but I'm swamped with other stuff so if you want to land this it may be faster to do it. It's not a massive change and waiting for me isn't really necessary. |
|
I don't have any immediate need for this. I was just triaging the PR queue a bit. |
|
Ok, I've set up some time to update this PR on Friday next week. |
|
Closing this and will re-open a correct one on the latest version |
This PR changes the
linker.get_default()deafult return value. It removes the return of a no-op function as this is rarely what users of the method would want. I have replaced it with an error that indicates that the module has no default functions to return.This has been briefly discussed in the zulip bytecode alliance channel.
I do not know how to add test cases to this, it seems that there were no tests around it, but I'm happy to add some if anyone could guide me on where to put them.
I am unsure who the right reviewer for this is.