Disso35 has joined #jruby
<Disso35> Is there better documentation for jrubyc besides `--help` output? `--dir` and `--prefix` don't explain their functionality very well
Liothen has quit [Ping timeout: 252 seconds]
Iambchop has quit [Ping timeout: 252 seconds]
<headius[m]> There's docs on the wiki and in the book, but that's sadly out of print
Liothen has joined #jruby
Iambchop has joined #jruby
<Disso35> I see, I ended up getting the result I wanted by `cd`ing into the source folder before running `jrubyc`, I'll stick with that for now
Disso35 has quit [Remote host closed the connection]
rusk has joined #jruby
drbobbeaty has joined #jruby
drbobbeaty has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
shellac has joined #jruby
_whitelogger has joined #jruby
drbobbeaty has joined #jruby
rsim has quit [Ping timeout: 252 seconds]
<headius[m]> Ok. May I ask why you are interested in jrubyc?
shellac has quit [Quit: Computer has gone to sleep.]
shellac has joined #jruby
shellac has quit [Ping timeout: 250 seconds]
xardion has quit [Remote host closed the connection]
rusk has quit [Remote host closed the connection]
xardion has joined #jruby
ilikeorangutans has joined #jruby
ilikeorangutans has quit [Client Quit]
drbobbeaty has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
ilikeorangutans has joined #jruby
<ilikeorangutans> hi friends of jruby, i'm looking at https://github.com/jruby/jruby/issues/5734#issuecomment-494024677 and I'm trying to understand how the specs in jruby even work
<ilikeorangutans> could i just paste the example code from the issue into a spec? Looking at the existing specs there seems to be a specific style of writing them
<headius[m]> We keep a copy of the specs under spec/ruby that you can edit directly, changes get merged back into the master copy
<headius[m]> With JRuby in PATH you can run those files directly or use spec/mspec/bin/mspec
<ilikeorangutans> There's a PR review process in place, right? could i just contribute a spec? I'm not sure if i can actually fix the issue
<headius[m]> Are you familiar with spec syntax?
<ilikeorangutans> very, very superficially
<headius[m]> Oh yes I just hoped you'd make some specs
<ilikeorangutans> i'll... try something haha
<headius[m]> Or see if this sort of case might be covered already
<headius[m]> Ok thanks 😀
<ilikeorangutans> https://github.com/jruby/jruby/blob/master/spec/ruby/core/enumerator/lazy/flat_map_spec.rb#L7 has only a line saying `it_behaves_like :enumerator_lazy_collect_concat, :flat_map`
<ilikeorangutans> i take it that refers to a different spec? in that case the other spec might not be correct
<ilikeorangutans> (or incomplete)
<headius[m]> Ok then there should be a "shared" spec that's used for multiple
<headius[m]> shared/ dir in same path likely
<headius[m]> Look at the requires in that file
<ilikeorangutans> ah gotcha
<ilikeorangutans> sorry, another question: when running specs with spec/mspec/bin/mspec, is there an easy way to run it with jruby instead of mri ruby?
ilikeorangutans has quit []
ilikeorangutans has joined #jruby
<lopex> just prefix mspec with jruby
<lopex> or use rbenv and the like ?
<lopex> headius[m]: is there something wrong with that azure ci, when I was at their console page, it was stalling (the ui)
<ilikeorangutans> i'm somewhat stumped. i wrote a small spec for the problem i ran into and it passes. however, the exact same code in IRB will fail. I ended up making the spec as literal as i could just to ensure i'm not tripping over something else: https://github.com/jruby/jruby/pull/5744/files
<ilikeorangutans> any idea why this would fail using running irb on jruby (from master) and pass in the spec (using same jruby version)?
<lopex> at parse or execution ?
<lopex> end end smells to me
<lopex> I'd put semicolon there
<lopex> not sure how syntax has changed recently though
<ilikeorangutans> hmmm good point, let me reformat just to be sure
travis-ci has joined #jruby
<travis-ci> jruby/jruby (master:15c9691 by Thomas E. Enebo): The build was broken. https://travis-ci.org/jruby/jruby/builds/535997465 [203 min 22 sec]
travis-ci has left #jruby [#jruby]
<lopex> not the case it seems
<lopex> just checked
<lopex> but well, havent checked under irb
<lopex> I hope lazy never spawns separate threads though ?
<lopex> otherwise I'm stumped too
<ilikeorangutans> same source location for both spec and irb so it's the _same_ code; wouldn't know about threads... i literally reported a bug and this is the first time i'm poking jruby sources haha
<lopex> no worries
<lopex> but class Foo; def foo; end end also seems to be working under irb
<lopex> under jruby
<ilikeorangutans> yeah; the syntax appears to be fine. just looking further into how lazy enumerators even work.
<ilikeorangutans> gotta say, a lot of stuff in the core library is not what i expected it to be
travis-ci has joined #jruby
travis-ci has left #jruby [#jruby]
<travis-ci> jruby/jruby (master:15c9691 by Thomas E. Enebo): The build was broken. https://travis-ci.org/jruby/jruby/builds/535997465 [220 min 35 sec]
<lopex> yeah, it;s juge
<lopex> *huge
<lopex> mri sources though are quite easy to read
<lopex> with exceptions
<lopex> I hate python sources otoh
<lopex> I'd rather read hotspot ones
<lopex> ilikeorangutans: did you get anywhere ?
<ilikeorangutans> no, not yet; i had to step away, dinner time here
<ilikeorangutans> depending on how much time i have i might take another stab at this tomorrow
<lopex> I bet the lazy part is the culprit
<lopex> falt_map just cant be that wrong