On Tue, Mar 20, 2018 at 2:19 AM, Joe Wolf <joew...@gmail.com> wrote: > [...] Glad there was consensus on the strict upper bound view for > upto/downto. [...] >
Being at the conference the last week, I didn't get time to look at that properly. It worries me that we'd have a different semantics for upto/downto compared to other classes but I can see the need for the proposed functionality. I was thinking that we might need to make the same kind of distinction that we do for Range, e.g. inclusive vs exclusive or that Java does in the Streams api, open/closed. But I'll play a little more and propose something more concrete. > On Mon, Mar 19, 2018 at 12:07 PM, Guillaume Laforge <glafo...@gmail.com> > wrote: > >> Cool! >> >> On Mon, Mar 19, 2018 at 5:06 PM, Daniel.Sun <sun...@apache.org> wrote: >> >>> Merged. >>> https://github.com/apache/groovy/pull/674 >>> >>> Cheers, >>> Daniel.Sun >>> >>> >>> >>> -- >>> Sent from: http://groovy.329449.n5.nabble.com/Groovy-Dev-f372993.html >>> >> >> >> >> -- >> Guillaume Laforge >> Apache Groovy committer & PMC Vice-President >> Developer Advocate @ Google Cloud Platform >> >> Blog: http://glaforge.appspot.com/ >> Social: @glaforge <http://twitter.com/glaforge> / Google+ >> <https://plus.google.com/u/0/114130972232398734985/posts> >> > >
