`await` is rejected in a `@this async` function, which compiles to an `async function`
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 3/5
- 预计耗时
- 1-2 天
- 新手友好度
- 72/100
- Issue 类型
- 缺陷
- 描述清晰度
- 描述清楚
- 活跃度
- 活跃
- 技术栈
- javascript, ocaml
调研方向
Start in compiler/frontend/bs_builtin_ppx.ml, where expr_mapper handles the Pexp_fun case with @this; compare its async_context handling with the plain Pexp_fun branch. Check the compiler tests for @this async functions and add coverage for await in the body. Done means the example compiles while await remains rejected in non-async @this functions and plain nested functions.
由索引模型根据 Issue 内容生成。
描述
An await in the body of a function that has both @this and async is rejected with "Await on expression not in an async context", although the function is typed as returning a promise and is compiled to a JavaScript async function.
type obj = {name: string}
let m = @this async (self: obj, x: promise<int>) => {
let v = await x
self.name ++ Int.toString(v)
}
We've found a bug for you!
ThisAsyncAwait.res:4:11-17
2 │
3 │ let m = @this async (self: obj, x: promise<int>) => {
4 │ let v = await x
5 │ self.name ++ Int.toString(v)
6 │ }
Await on expression not in an async context
Without the await, a @this async function has type @this (obj, int) => promise<string> and compiles to an async function, where await is valid:
let m = @this async (self: obj, x: int) => self.name ++ Int.toString(x)
async function m(x) {
let self = this ;
return self.name + x.toString();
}
module M = await List and for await x of xs {...} in the body of a @this async function are rejected with the same error. To use await, the body has to go into a separate async function that the method calls:
let helper = async (self: obj, x: promise<int>) => {
let v = await x
self.name ++ Int.toString(v)
}
let m = @this (self: obj, x: promise<int>) => helper(self, x)
async function helper(self, x) {
let v = await x;
return self.name + v.toString();
}
function m(x) {
let self = this ;
return helper(self, x);
}
In compiler/frontend/bs_builtin_ppx.ml, expr_mapper handles a Pexp_fun with @this (the Meth_callback case of Ast_attributes.process_attributes_rev) by setting async_context := false and then calling Ast_uncurry_gen.to_method_callback ~async, which maps the body under that context and builds the function with ~async and Ast_async.make_function_async ~async. So the body is checked as non-async even when the function it is emitted into is async. The false dates from when a @this function could not be async; #7702 passed ~async to to_method_callback but left the context unchanged. Setting async_context := async in that branch, as the plain Pexp_fun branch above it does, fixes it: the example at the top then compiles to async function m(x) with let v = await x;, and m.call({name: "n"}, Promise.resolve(41)) resolves to "n41". await in a @this function without async, or in a plain function inside a @this async one, is still rejected.
Reproduced with 12.0.0-beta.3, 12.3.1, 13.0.0-alpha.6 and master (fc7444266). A @this async function compiles to an async function with a promise result since #7702 (12.0.0-beta.3), the fix for #7681. Before that, in 12.0.0-beta.2 and 11.1.4, it compiled to a plain function, and await in it was rejected as well.
#6100 reported this error together with the dropped async attribute; #6105 fixed the attribute. Its first example, where the async function is the one returned by the @this function (@this self => async arg => await ...), compiles since 13.0.0-alpha.6; the form above, with @this and async on the same function, does not.
Related: #6100, #7681, #7702.
- 主要语言
- OCaml
- 星标
- 7.5k
- 派生
- 485
- 平均合并
- 17 小时 9 分钟
- 30 天内合并 PR
- 264
环境准备
在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
rescript-lang/rescript 的其他 Issue
-
Exception analysis does not know the Temporal `fromStringOrThrow` functions可能已有人在做 @cknitt 于 1 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 72/100
rescript-lang/rescript#9182 ·
维护者通常 1 天内回复
-
难度 5/5 一周以上 新手友好度 25/100
rescript-lang/rescript#9233 ·
维护者通常 1 天内回复
-
难度 4/5 3-5 天 新手友好度 55/100
rescript-lang/rescript#9230 ·
维护者通常 1 天内回复
-
难度 4/5 3-5 天 新手友好度 44/100
rescript-lang/rescript#9228 ·
维护者通常 1 天内回复
-
难度 4/5 3-5 天 新手友好度 45/100
rescript-lang/rescript#9227 ·
维护者通常 1 天内回复
查看 rescript-lang/rescript 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 78/100
NVIDIA-RTX/NRI#312 ·
维护者通常 1 天内回复
-
502 on Node 26: ERR_INVALID_ARG_VALUE: Setting the TLS ServerName to an IP address is not permitted未关闭
难度 2/5 1-3 小时 新手友好度 76/100
-
难度 2/5 1-3 小时 新手友好度 64/100
NucleusFramework/Nucleus#912 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 71/100
streetcomplete/StreetComplete#7364 · 7 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 1 天内回复