-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Usability of TExecutor::MapReduce #7871
Labels
Projects
Comments
We should have better SFINAE code that provides clearer errors
I think |
peremato
added a commit
to peremato/root
that referenced
this issue
Feb 14, 2024
peremato
added a commit
to peremato/root
that referenced
this issue
Feb 14, 2024
Adding an
|
dpiparo
pushed a commit
that referenced
this issue
Feb 23, 2024
gwmyers
pushed a commit
to gwmyers/root
that referenced
this issue
Feb 23, 2024
kristupaspranc
pushed a commit
to kristupaspranc/root
that referenced
this issue
Apr 10, 2024
lobis
pushed a commit
to lobis/root
that referenced
this issue
Apr 10, 2024
kristupaspranc
pushed a commit
to kristupaspranc/root
that referenced
this issue
May 21, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Explain what you would like to see improved
It's hard to use TExecutor::MapReduce correctly, because the required signature of the reducer isn't mentioned in the documentation.
Optional: share how it could be improved
[](const std::vector<T>&) { }
Failure to meet that signature leads to an explosion of template instantiation failures with gcc.
Map()
?Map()
always has to return a dummy value (or: Fix TExecutorCRTP::Map() should support void #7872 )To Reproduce
The text was updated successfully, but these errors were encountered: