Fix name clash of RNG with shared memory #1904
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
RNG uses
auto offset = philox_args.captured_ ? ....
Shared memory uses
So when a scheduler tries to schedule RNG with shared memory, compilation will fail
This is NOT a new bug introduced in #1888, but instead, both names have been there for a long time. It is just I recently added both a test of RNG with broadcasting and a transpose scheduler.
In general, we should avoid common names like
offset
, we should usehow_you_will_use_it_offset
instead.