From: Yusuke Endoh <mame@...>
Date: 2011-10-31T21:13:10+09:00
Subject: [ruby-core:40555] [ruby-trunk - Feature #5321][Assigned] Introducing Numeric#exact? and Numeric#inexact?


Issue #5321 has been updated by Yusuke Endoh.

Status changed from Rejected to Assigned

Oops, sorry, I've closed this ticket by error.  Reopen.

-- 
Yusuke Endoh <mame@tsg.ne.jp>
----------------------------------------
Feature #5321: Introducing Numeric#exact? and Numeric#inexact?
http://redmine.ruby-lang.org/issues/5321

Author: Kenta Murata
Status: Assigned
Priority: Normal
Assignee: Yukihiro Matsumoto
Category: 
Target version: 


Ruby has several numeric classes such as Integer.
These classes are classified whether their instances represent numbers exactly.
According to this, Integer and Rational are exact, and Float and BigDecimal are inexact because they're always including error.
The exactness of a Complex depends on its real and imaginary parts.

Now, Ruby's numeric classes doesn't provide predicators to investigate the exactness of their instances.
So, if we want to examine whether a number is exactly zero, we must investigate the class of the number.
I want simple way to examine the number exactness.

I propose to introduce Numeric#exact? and/or Numeric#inexact? for resolving this inconvenience.



-- 
http://redmine.ruby-lang.org