subbu has quit [Quit: Leaving]
subbu has joined #jruby
subbu has quit [Quit: Leaving]
_whitelogger has quit [Ping timeout: 264 seconds]
_whitelogger has joined #jruby
<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.
<enebo[m]> edipo.federle: are you putting a println into that source code?
<edipofederle[m]> enebo: I'm using GDB... I am investigate a big deeper now, but still confussing :d
<enebo[m]> yeah I mean I assume begin will be 4 in the above and end will be nil
<enebo[m]> MRI does give the answer based on 4 and -5 so I am surprised to see it different at that point
<edipofederle[m]> Yep, I am checking here:
<edipofederle[m]> that is where MRI initialize range step begin/end
<enebo[m]> This may be obvious question but are you sure you are not hitting an earlier ranges breakpoint?
<enebo[m]> I know by default MRI will load rubygems for example
<edipofederle[m]> Yes, I am sure, I'm looking at it when I "see" that is my code begins evaluated.
<edipofederle[m]> I will try check a bit more, and I let you know which more details and example, maybe
<enebo[m]> My other thought is I don't know how tagged integers print out
<edipofederle[m]> s/which/with/
<enebo[m]> beg and end are VALUE but they mark a bit to not really heap alloc
<edipofederle[m]> good point
<enebo[m]> deeper in this code they will make a long/int out of this
<enebo[m]> err not even yet in this method
<enebo[m]> since it will make the arithseq here
<edipofederle[m]> I will try check in that direction so
<enebo[m]> I mean I would assume it is a high bit so I would have thought you would see a large negative
<enebo[m]> This is the line you get to though this point it is still just a VALUE
<enebo[m]> but I am grasping a little bit seems fairly clear this would not work if it was not begin of 4 and step of -5
<edipofederle[m]> yep
<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)
<enebo[m]> in this case I feel on the Java side you just take the values you would expect 4, nil, -5
<enebo[m]> but I can see why you are trying to understand why you are not seeing what you expect
<edipofederle[m]> enebo[m]: Actually, just curiosity on how it works on MRI side..
<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
<enebo[m]> yeah
<enebo[m]> Makes sense
<edipofederle[m]> great! Thanks for the points
<enebo[m]> Yeah fixnum representation is explained here and it does answer the question
<edipofederle[m]> cool
<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?
<enebo[m]> if not I think there is something people use so they can properly print out a VALUE
<edipofederle[m]> Yes, this is true
<enebo[m]> cool. Now I am again curious to use gdb :)
subbu has joined #jruby
<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'
<edipofederle[m]> Waiting for a self-hosted or a hosted runner to pickup this job..." is normal now on CI tasks?
<enebo[m]> edipo.federle: I have not seen that yet but hmm
nilsding has joined #jruby
subbu has quit [Quit: Leaving]
subbu has joined #jruby
subbu has quit [Quit: Leaving]