[Question] Should single-argument sender adaptors be sender adaptor closure objects?
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 3/5
- 预计耗时
- 1-3 小时
- 新手友好度
- 25/100
- Issue 类型
- 文档
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- cpp
- 领域
- api, documentation
调研方向
The question is about the wording of the C++ draft standard paragraph exec.adapt.obj#4, which says single-argument pipeable sender adaptors are closure objects. Compare it with the range adaptor closure wording in the standard and check how stdexec's single-argument sender adaptors are used with and without parentheses. This needs a decision from the maintainers in the thread, not a patch. Done means the maintainers confirm the intended syntax, and any wording fix they agree on is proposed.
由索引模型根据 Issue 内容生成。
描述
Hi @ericniebler,
I have a question regarding sender adaptors: are single-argument sender adaptors intended to be sender adaptor closure objects?
According to exec.adapt.obj#4 in the current draft standard:
"If a pipeable sender adaptor object accepts only one argument, then it is a pipeable sender adaptor closure object."
If I understand correctly, this implies that single-argument sender adaptors like into_variant, affine, and stopped_as_optional should be piped as sndr | into_variant rather than sndr | into_variant().
In std::ranges, single-argument range adaptors (such as views::all or views::keys) are indeed range adaptor closure objects, piped like rng | views::all. Was this design deliberately adopted for sender adaptors as well, or was this paragraph inadvertently copy-pasted from the range adaptor wording? In other words, is sndr | adaptor intended here, or is this a wording defect and it should have been sndr | adaptor()?
- 主要语言
- C++
- 星标
- 2.5k
- 派生
- 284
- 平均合并
- 2 天 32 分钟
- 30 天内合并 PR
- 88
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
NVIDIA/stdexec 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 68/100
维护者通常 1 天内回复
-
exec::start_now: request_stop() on the storage does not reach the senders可能已有人在做 @Nas01010101 今天认领。 未关闭
难度 3/5 1-2 天 新手友好度 25/100
维护者通常 1 天内回复
-
难度 4/5 1-2 天 新手友好度 45/100
维护者通常 1 天内回复
-
难度 4/5 3-5 天 新手友好度 25/100
维护者通常 1 天内回复
-
难度 4/5 一周以上 新手友好度 18/100
维护者通常 1 天内回复
相似的 Issue
-
enhancement
难度 2/5 1-3 小时 新手友好度 68/100
metasequoiaime/msime#10989 ·
维护者通常 1 天内回复
-
documentation good first issue help wanted
难度 2/5 1-3 小时 新手友好度 85/100
vek-language/vek-lang#1 · 1 条评论 ·
-
难度 2/5 1-3 小时 新手友好度 72/100
eclipse-score/lifecycle#957 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 62/100
mw00/project-maya#877 ·
维护者通常 1 天内回复