Currently, if you want to use new-style ranges, you have to awkwardly combine two of them, like shown here. This patch allows defining both ends of the range in one operator.
I'm not sure what kind of emphasis this project has on backwards compatibility, but if someone has code calling the ESRangeOp constructor with the boost parameter used by position, this will cause them problems. You can add a line testing whether op2 is a number, and if so assign it to boost or throw an Exception. Or you can reject the PR altogether. I won't be offended.
(Personally I think usage of the boost parameter is too rare to worry about).
Currently, if you want to use new-style ranges, you have to awkwardly combine two of them, like shown here. This patch allows defining both ends of the range in one operator.
I'm not sure what kind of emphasis this project has on backwards compatibility, but if someone has code calling the
ESRangeOp
constructor with the boost parameter used by position, this will cause them problems. You can add a line testing whetherop2
is a number, and if so assign it toboost
or throw an Exception. Or you can reject the PR altogether. I won't be offended.(Personally I think usage of the boost parameter is too rare to worry about).