feat: use generics for RangeBuilder #824
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.
Very small PR to use generics instead of
any
as type for the slices passed toRangeBuilder
The reason this is useful is because
[]any
forces the type to be an interface and a, for example, string slice[]string{}
can't be cast to[]interface{}
due to how slices work in Go.Example:
Go compile error:
When using the
rangeOverG
function the user of the function can pass any data type provided the receiving function has the right signature