type issue of let error

Open
#1,564 15 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
cpp
Domain
backend

Research direction

The issue names let_error, sender composition through |, lambda error types, and std::exception_ptr, but provides no file, test, or minimal reproducer. Start by reducing the reported type mismatch to a small let_error composition and determine whether differing sender error types are intended to compose; done means an agreed behavior and documented or tested resolution.

Written by the indexing model from the issue text.

Description

Looks like I am getting very weird compilation when trying to use let_error. I cannot specify type of the lambda to be either the actual error type nor std::exception_ptr. When I try to specify one of them, the compiler will complain it is not a well formed sender.

Looks like the problem is if some sender specify a different error type then they are not composable through |. I wonder whether this is intended and whether there are some recommended pattern for doing this?

Dominant language
C++
Stars
2.4k
Forks
270
Avg merge
2d 17h
Merged PRs (30d)
37

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from NVIDIA/stdexec

All issues in NVIDIA/stdexec

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.