Antiarc has quit [Read error: Connection reset by peer]
Antiarc has joined #jruby
shellac has joined #jruby
subbu is now known as subbu|lunch
subbu|lunch is now known as subbu
shellac has quit [Ping timeout: 240 seconds]
drbobbeaty has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
rdubya has quit [Quit: Leaving.]
joast has joined #jruby
shellac has joined #jruby
shellac has quit [Ping timeout: 255 seconds]
drbobbeaty has joined #jruby
shellac has joined #jruby
shellac has quit [Ping timeout: 240 seconds]
kith has joined #jruby
<headius>
range is green, proc is green
<headius>
I am bored
<GitHub46>
[jruby] headius pushed 4 new commits to ruby-2.4: https://git.io/v7JXK
<GitHub46>
jruby/ruby-2.4 171d2e2 Charles Oliver Nutter: Pass block through curried proc.
<GitHub46>
jruby/ruby-2.4 d612739 Charles Oliver Nutter: Check frozen during Range#initialize.
<GitHub46>
jruby/ruby-2.4 d15def1 Charles Oliver Nutter: Fix type error for bad buffer kwarg to Array#pack.
<lopex>
headius: do they still use ivars for core structs ?
<headius>
some, like Range
<lopex>
I know it helps them simplify the core RObject unions etc
<headius>
depends how far you get from the original classes
<lopex>
but still, why
<headius>
yeah they have so many different R types now I don't see why they wouldn't apply it to all popular structures
<headius>
Range, Time, Exception using inaccessible ivars is a smell to me
<lopex>
maybe they think, since they introduced those unions it will help gc pressure nontheless
<headius>
also makes it harder for us to use actual fields (e.g. real structs like MRI should use) because they expect certain types to always be marshaled as "has ivars"