<kares[m]>
and since there's `Double::Type` the `java.lang.Class` gets into JI causing `java.lang.reflect` a few classes from `java.lang.reflect` to get into JI
<kares[m]>
* and since there's `Double::Type` the `java.lang.Class` gets into JI causing `java.lang.reflect` a few classes from `java.lang.reflect` to init
<kares[m]>
guess its the usual dilema - load less code at startup or now, a trivial fix would be to not `java_import` those in range.rb
<headius[m]>
Ahh I see
<kares[m]>
* guess its the usual dilema - load less code at startup or not, a trivial fix would be to not `java_import` those in range.rb
<headius[m]>
There's just a couple uses...could be bound as JRuby::Util methods
<headius[m]>
Or we just port this into Java
<headius[m]>
The backports library uses pack and unpack to get the float bits
<headius[m]>
Slow but works I suppose
Antiarc has quit [Ping timeout: 265 seconds]
haze has quit [Ping timeout: 260 seconds]
Antiarc has joined #jruby
haze has joined #jruby
<kares[m]>
or we could have a java_import 'java.lang.Double', load: false
<kares[m]>
probably not worth the hustle ... seems it would complicate things a bit
shellac has joined #jruby
<kares[m]>
either way (also just doing `java.lang.Double.doubleToLongBits`) is fine by me ...
<kares[m]>
`Math` is not needed since we could just `double.abs`
shellac has quit [Quit: Computer has gone to sleep.]
<headius[m]>
I tried using Float#abs and it didn't work the same
<headius[m]>
I think it had different behavior around Infinity
<headius[m]>
kares: I'm just going to add those as utility methods on BSearch that are implemented in Java
<headius[m]>
no imports or JI needed at all then
<kares[m]>
binary search on an infinite range? did not realize its supported 😉
<headius[m]>
there's the basics... just cleaning up now
<headius[m]>
I'll just go ahead with this and revert my test change... any further improvements are welcome
<headius[m]>
kares: thanks, seems like that was it
KeyJoo has joined #jruby
lucasb has joined #jruby
<jeremyevans>
headius[m]: I think all of those cases were existing tests that originally used DateTime, and after ruby 2.6 was release I added support for Time using the new timezone API in 2.6, then figured out they could actually be supported without the timezone API
<jeremyevans>
headius[m]: Anyway, it's good that Sequel is helping you find issues prior to release :)
<headius[m]>
yeah I'll have to dig into these and see what we're not doing right
<headius[m]>
all the new Time tests and specs are passing so it's edges that didn't get tests
<headius[m]>
I did tag a couple things I thought were obscure or minor differences but I'll revisit those