09:25 <edipofederle[m]> enebo: I mean, for example, given: `#p [0,1,2,3,4,5,6,7,8,67,645,34][(4..).step(-5)]`, how at the point in the code I paste on GIST, the aseq.beg and aseq.end as calculated with 8 and 9, respectively.

14:54 <enebo[m]> edipo.federle: are you putting a println into that source code?

14:55 <edipofederle[m]> enebo: I'm using GDB... I am investigate a big deeper now, but still confussing :d

14:55 <enebo[m]> yeah I mean I assume begin will be 4 in the above and end will be nil

14:56 <enebo[m]> MRI does give the answer based on 4 and -5 so I am surprised to see it different at that point

14:56 <edipofederle[m]> Yep, I am checking here: https://github.com/ruby/ruby/blob/master/range.c#L439

14:56 <edipofederle[m]> that is where MRI initialize range step begin/end

14:57 <enebo[m]> This may be obvious question but are you sure you are not hitting an earlier ranges breakpoint?

14:58 <enebo[m]> I know by default MRI will load rubygems for example

14:59 <edipofederle[m]> Yes, I am sure, I'm looking at it when I "see" that is my code begins evaluated.

14:59 <edipofederle[m]> I will try check a bit more, and I let you know which more details and example, maybe

14:59 <enebo[m]> My other thought is I don't know how tagged integers print out

14:59 <edipofederle[m]> s/which/with/

15:00 <enebo[m]> beg and end are VALUE but they mark a bit to not really heap alloc

15:00 <edipofederle[m]> good point

15:00 <enebo[m]> deeper in this code they will make a long/int out of this

15:01 <enebo[m]> err not even yet in this method

15:01 <enebo[m]> since it will make the arithseq here

15:01 <edipofederle[m]> I will try check in that direction so

15:01 <enebo[m]> I mean I would assume it is a high bit so I would have thought you would see a large negative

15:02 <enebo[m]> https://github.com/ruby/ruby/blob/master/range.c#L458

15:02 <enebo[m]> This is the line you get to though right...at this point it is still just a VALUE

15:03 <enebo[m]> but I am grasping a little bit here...it seems fairly clear this would not work if it was not begin of 4 and step of -5

15:03 <edipofederle[m]> yep

15:04 <enebo[m]> I usually just read the code and I when I am curious I usually build with some printlns (which is really rare because I usually understand the intent enough)

15:04 <enebo[m]> in this case I feel on the Java side you just take the values you would expect 4, nil, -5

15:04 <enebo[m]> but I can see why you are trying to understand why you are not seeing what you expect

15:05 <edipofederle[m]> enebo[m]: Actually, just curiosity on how it works on MRI side..

15:05 <enebo[m]> On JRuby side this endless is already making the right thing but we do not handle it in Array#[] yet as an argument

15:05 <enebo[m]> yeah

15:05 <enebo[m]> Makes sense

15:06 <edipofederle[m]> great! Thanks for the points

15:06 <enebo[m]> edipo.federle: https://devdriven.com/2008/01/ruby-internals-why-ruby_fixnum_flag-should-be-0x00/

15:07 <enebo[m]> Yeah fixnum representation is explained here and it does answer the question

15:08 <edipofederle[m]> cool

15:09 <enebo[m]> I think we talked about gdb like 1/2 a year ago right? There was some file people used so they could run things like inspect() on values?

15:09 <enebo[m]> if not I think there is something people use so they can properly print out a VALUE

15:10 <edipofederle[m]> Yes, this is true

15:10 <enebo[m]> cool. Now I am again curious to use gdb :)

17:38 <edipofederle[m]> The "Can't find any online and idle self-hosted or hosted runner in the current repository, account/organization that matches the required labels: 'ubuntu-latest'

17:38 <edipofederle[m]> Waiting for a self-hosted or a hosted runner to pickup this job..." is normal now on CI tasks?

18:37 <enebo[m]> edipo.federle: I have not seen that yet but hmm