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.

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

EQUIV? decimal! comparison not exact enough to be transitive #1134

Closed
Siskin-Bot opened this issue Feb 15, 2020 · 0 comments
Closed

EQUIV? decimal! comparison not exact enough to be transitive #1134

Siskin-Bot opened this issue Feb 15, 2020 · 0 comments
Labels

Comments

@Siskin-Bot
Copy link
Collaborator

Submitted by: Ladislav

the original idea was that the EQUIV? comparison would be finer than the EQUAL? function and transitive. The test below yielding False proves that the EQUIV? comparison isn't transitive currently.

[not equiv? to decimal! #{3FD3333333333333} to decimal! #{3FD3333333333334}]

Imported from: CureCode [ Version: alpha 76 Type: Bug Platform: All Category: Native Reproduce: Always Fixed-in:none ]
Imported from: metaeducation#1134

Comments:

Rebolbot commented on Jul 23, 2009:

Submitted by: BrianH

Changed to a bug, and reworded the summary accordingly.


Rebolbot commented on Nov 4, 2010:

Submitted by: Ladislav

in the core-tests suite

Rebolbot mentioned this issue on Jan 22, 2016:
[Epic] Backwards-incompatible API changes, for the greater good


Rebolbot added Type.bug and Test.written on Jan 12, 2016


Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants