Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

FloatRange: new type for accurate floating-point ranges [fix #2333] #5636

Merged
merged 4 commits into from
Feb 24, 2014
Merged

FloatRange: new type for accurate floating-point ranges [fix #2333] #5636

merged 4 commits into from
Feb 24, 2014

Commits on Feb 24, 2014

  1. FloatRange type: correct/intuitive floating-point ranges (no syntax). 

    This addresses the core behvaioral problems of #2333 but doesn't yet
hook up the colon syntax to constructing FloatRange objects [#5885].
    @StefanKarpinski
    StefanKarpinski committed Feb 24, 2014
    Configuration menu
    Copy the full SHA
    47a3447 View commit details
    Browse the repository at this point in the history

  2. FloatRange: hook new type up to colon syntax [fixes #2333].

    @StefanKarpinski
    StefanKarpinski committed Feb 24, 2014
    Configuration menu
    Copy the full SHA
    f4905d9 View commit details
    Browse the repository at this point in the history

  3. FloatRange: slightly more conservative test for lifting in frange. 

    There's a slight chance that computing `stop` with integers and then
converting to floating point would work but doing to computation in
floating point would not give the correct answer. This tests actual
values – with the correct type – that will be used.
    @StefanKarpinski
    StefanKarpinski committed Feb 24, 2014
    Configuration menu
    Copy the full SHA
    0e0e1d9 View commit details
    Browse the repository at this point in the history

  4. FloatRange: work around for #5885 – temporarily move colon defintion 

    Obviously we don't want to leave things like this, but with this
work around, we can merge the FloatRange branch and figure out the
root cause of #5885 later.
    @StefanKarpinski
    StefanKarpinski committed Feb 24, 2014
    Configuration menu
    Copy the full SHA
    75efb44 View commit details
    Browse the repository at this point in the history