Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Does `task.return`'s memory strictly match the canon-lifted function, or only match when present?

未关闭
#749 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 2 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
18/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
wasm
领域
api

调研方向

The check lhs.memory is rhs.memory for task.return is in the spec text on async canonical built-ins, and the mismatch is at test/async/cross-abi-calls.wast around line 143. Read the validation rules for task.return and canon lift, then the test, to see where the memory check applies. Done means maintainers decide whether the spec text or the test changes, and a follow-up change makes the two agree. The open question is a design decision, so confirm the direction in the thread before writing any change.

由索引模型根据 Issue 内容生成。

描述

Currently the spec indicates that the check to perform is lhs.memory is rhs.memory, and my understanding of this is that the two need to be strictly equal (if one's specified the other must be, etc). My understanding is that this additionally needs to be checked even if the result type doesn't need a memory.

However test/async/cross-abi-calls.wast currently has a mismatch here where task.return does not contain memory but the canon lifted function does.

IIRC we discussed this in the past but I'm kind of forgetting the outcomes -- is this something where the spec text needs an update? Or the tests?

主要语言
WebAssembly
星标
1.4k
派生
132
平均合并
4 天
30 天内合并 PR
12

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

WebAssembly/component-model 的其他 Issue

查看 WebAssembly/component-model 的全部 Issue

相似的 Issue

更多 Backend & API Design Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。