You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It appears to be deliberate. Whenever there is an assert_trap, it checks whether you're about to declare a module, and if so creates an assert_uninstantiable instead. Code from wabt:
Result WastParser::ParseAssertTrapCommand(CommandPtr* out_command) {
WABT_TRACE(ParseAssertTrapCommand);
EXPECT(Lpar);
EXPECT(AssertTrap);
if (PeekMatchLpar(TokenType::Module)) {
auto command = MakeUnique<AssertUninstantiableCommand>();
CHECK_RESULT(ParseScriptModule(&command->module));
CHECK_RESULT(ParseQuotedText(&command->text));
*out_command = std::move(command);
} else {
auto command = MakeUnique<AssertTrapCommand>();
CHECK_RESULT(ParseAction(&command->action));
CHECK_RESULT(ParseQuotedText(&command->text));
*out_command = std::move(command);
}
EXPECT(Rpar);
return Result::Ok;
}
I unexpectedly saw
AssertUninstantiable
while parsing wast files that do not containassert_uninstantiable
.Expected:
Actual:
Example:
The text was updated successfully, but these errors were encountered: