What are your thoughts on supporting double weights, instead of integer weights only? This would allow to use (0..1] weights, which would be more convenient than mapping those weights to integers in user code.
This would require to distinguish the semantics of count from weight, which could be beneficial in other use cases as well, e.g. #198.
Obviously, this will introduce a breaking change to the API.
What are your thoughts on supporting double weights, instead of integer weights only? This would allow to use
(0..1]weights, which would be more convenient than mapping those weights to integers in user code.This would require to distinguish the semantics of
countfromweight, which could be beneficial in other use cases as well, e.g. #198.Obviously, this will introduce a breaking change to the API.