From: "matz (Yukihiro Matsumoto)" <matz@...>
Date: 2012-12-06T23:28:46+09:00
Subject: [ruby-core:50633] [ruby-trunk - Feature #7517] Fixnum::MIN,MAX


Issue #7517 has been updated by matz (Yukihiro Matsumoto).

Assignee set to mame (Yusuke Endoh)
Target version changed from next minor to 2.0.0

Endo san, since it's a small and useful change, can I merge this for 2.0 even after spec freeze?
Of course, you can reject as a release manager. In that case, file this proposal as "next minor" again.

Matz.

----------------------------------------
Feature #7517: Fixnum::MIN,MAX
https://bugs.ruby-lang.org/issues/7517#change-34479

Author: matz (Yukihiro Matsumoto)
Status: Open
Priority: Normal
Assignee: mame (Yusuke Endoh)
Category: core
Target version: 2.0.0


Maximum (or minimum) number of fixnum can not be get in portable fashion, so I propose Fixnum::MAX and Fixnum::MIN just like Float::MAX and Float::MIN.

Matz


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