[yast-devel] Heads-up: ruby-2.4.0-preview1 unifies Fixnum and Bignum
Hi, ruby-2.4 includes a feature named "Unify Fixnum and Bignum into Integer" https://www.ruby-lang.org/en/news/2016/06/20/ruby-2-4-0-preview1-released/ https://bugs.ruby-lang.org/issues/12005 I have installed it with rbenv and found that the constants Fixnum and Bignum still exist, but resolve to the Integer class. So our code referencing Fixnum should still work. https://github.com/search?utf8=%E2%9C%93&q=is_a%3F+Fixnum+org%3Ayast&type=Code&ref=searchresults OTOH, we also have Yast::Integer, so considering the "fun" we are having with ::String and Yast::String we may be better off removing Yast::Integer before we uprade to ruby-2.4 http://www.rubydoc.info/github/yast/yast-yast2/Yast/IntegerClass -- Martin Vidner, YaST Team http://en.opensuse.org/User:Mvidner Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu
Dne 20.6.2016 v 17:37 Martin Vidner napsal(a): [...]
OTOH, we also have Yast::Integer, so considering the "fun" we are having with ::String and Yast::String we may be better off removing Yast::Integer before we uprade to ruby-2.4 http://www.rubydoc.info/github/yast/yast-yast2/Yast/IntegerClass
Yast::Integer is used only at few places and it can be easily replaced by native Ruby methods like Array#min/max or by native Ruby Range class, e.g. (start...stop).to_a. So removing Yast::Integer should be quite easy... -- Ladislav Slezák Appliance department / YaST Developer Lihovarská 1060/12 190 00 Prague 9 / Czech Republic tel: +420 284 028 960 lslezak@suse.com SUSE -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On Mon, 20 Jun 2016 18:26:35 +0200, Ladislav Slezak
Dne 20.6.2016 v 17:37 Martin Vidner napsal(a): [...]
OTOH, we also have Yast::Integer, so considering the "fun" we are having with ::String and Yast::String we may be better off removing Yast::Integer before we uprade to ruby-2.4 http://www.rubydoc.info/github/yast/yast-yast2/Yast/IntegerClass
Yast::Integer is used only at few places and it can be easily replaced by native Ruby methods like Array#min/max or by native Ruby Range class, e.g. (start...stop).to_a.
So removing Yast::Integer should be quite easy...
so create a fate / PBI for that together with some references? M. -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
participants (3)
-
Ladislav Slezak -
Martin Vidner -
Michal Filka