`inline_scheduler` doesn't advertise scheduler, cause spawn_future fail to compile with task
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
Research direction
Start with the inline_scheduler implementation and the compiler-explorer reproduction involving schedule, get_completion_scheduler, let_value, and spawn_future. Compare the behavior with the exec.sched requirement and existing scheduler-related tests; done means the example compiles without breaking the tests.
Written by the indexing model from the issue text.
Description
according to exec.sched
For a given scheduler expression sch, the expression get_completion_scheduler<set_value_t>(get_env(schedule(sch))) shall compare equal to sch.
stdexec::inline_scheduler seems doesn't conform it.
which cause the following code fail to compile (compiler explorer):
ex::task<int> foo() { co_return 1; }
int main() {
ex::simple_counting_scope scope;
auto task = ex::inline_scheduler {}.schedule() | ex::let_value([foo = foo()]() mutable { return std::move(foo); });
ex::spawn_future(std::move(task), scope.get_token());
}
I tried to add a query(get_completion_scheduler_t<set_value_t>) to it, but it broke a lot of tests. I wonder whether I understand it correctly?
- Dominant language
- C++
- Stars
- 2.4k
- Forks
- 270
- Avg merge
- 3d 6h
- Merged PRs (30d)
- 39
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from NVIDIA/stdexec
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
Difficulty 4/5 3-5 days Newbie friendliness 66/100
-
Difficulty 3/5 1-2 days Newbie friendliness 74/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
Sensor initialization takes very long when `--initial-sim-time` is set to current UNIX timestamp Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
gazebosim/gz-sensors#662 · 1 comment ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
comp-datalake
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ClickHouse/ClickHouse#121222 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
LadybirdBrowser/ladybird#12123 ·