Support `component-model-async` in the component-model and GC implementation

未关闭
#15,080 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
rust, wasm
领域
backend, compilers

调研方向

Start with the linked discussion and the referenced code in crates/wasmtime/src/runtime/component/concurrent.rs around line 3053 to understand the GC ABI limitation. The issue calls for supporting component-model-async across the component-model and GC implementation; determine the affected integration points and tests from that investigation. Done means async component-model support handles GC correctly, including rooting and parameter/result limits.

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

描述

wasm-proposal:component-model wasm-proposal:gc

https://github.com/bytecodealliance/wasmtime/pull/15051#discussion_r4413744525

FWIW I think that the concurrent code is going to need some relatively invasive changes to handle the GC ABI. Not only because of rooting everywhere but also because limits/maximums in params/results are pretty heavily baked in to the implementation on the host side. It might be best to just reject this for now and have a separate todo! or component-model-async integration being a big TODO item.

For example there's code like this which is definitely not correct for GC.

主要语言
Rust
星标
18.8k
派生
1.9k
平均合并
23 小时 6 分钟
30 天内合并 PR
410

环境准备

从这里开始

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

bytecodealliance/wasmtime 的其他 Issue

查看 bytecodealliance/wasmtime 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 发到你的邮箱

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