Skip to content
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

[Breaking] &Option<T> -> Option<&T> in nccl broadcast. Add Option argument to nccl reduce. #292

Merged
merged 2 commits into from
Jan 8, 2025

Conversation

coreylowman
Copy link
Owner

Resolves #290

@coreylowman coreylowman changed the title [Breaking] &Option<T> -> Option<&T> in nccl broadcast. Add Option argument to nccl reduce. [Breaking][Waiting to merge] &Option<T> -> Option<&T> in nccl broadcast. Add Option argument to nccl reduce. Sep 6, 2024
@coreylowman coreylowman changed the title [Breaking][Waiting to merge] &Option<T> -> Option<&T> in nccl broadcast. Add Option argument to nccl reduce. [Breaking] &Option<T> -> Option<&T> in nccl broadcast. Add Option argument to nccl reduce. Jan 8, 2025
@coreylowman coreylowman merged commit a52465d into main Jan 8, 2025
14 checks passed
@coreylowman coreylowman deleted the 290-nccl-option branch January 8, 2025 13:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Should nccl::broadcast take a Option<&T> instead of an &Option<T>?
1 participant