fix: fix errors regarding Reducer functionalities in segment.cpp #100
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.
This fixes two different errors regarding the reducer functionality in segment.cpp.
First of all, the AT_DISPATCH_REDUCTION_TYPES macro places the declaration of REDUCE in different conditional scopes, which causes the compiler (cl.exe in my case) to fail since REDUCE is then only defined if one of the if scopes is entered. The lambda thrown in as a second argument doesn't seem to be able to catch that variable either. This is easily fixed by defining REDUCE once before differentiating between the types.
Secondly, making the ReductionType a template argument of the Reducer forces us to define the ReductionType at runtime (as a constant expression), which isn't happening, causing another error at compile time. Since the Reducer doesn't have any internal state and all functions only operate on their parameters, we can safely move the ReductionType into the parameter list of the functions. This fixes the second error. As a neat plus we also don't need to create an instance of every possible ReducerType using the template to call the Reducer with every possible type.