Vadim Belman
Vadim Belman
BTW, what's your `$LD_LIBRARY_PATH` is set to?
I would suggest moving the sub into PseudoStash and making it a static method. Correspondingly, `Actions` code would produce method calls for dynamic lookups.
@jnthn you're fast! Actually, Actions does this: ``` $past := QAST::Op.new( :op('call'), :name('&DYNAMIC'), $*W.add_string_constant($name)); ``` Do you suggest replacing `:name('&DYNAMIC')` with `$*W.find_symbol(:setting-only)`? I'm simplifying because don't remember if the op...
> > Anyway, I like the idea of moving it into PseudoStash a bit more because they basically do the same thing. > > It'd have worse code size, though....
@Xliff This is not really a matter of language specification because neither of language behaviours are changing. Just a technical implementation which could happen any time when its ready.
@CIAvash as you mentioned this issue, have you been working on this project lately?
The first thing coming to mind when considering the LTS is a case where a bug fix for a problem existing in an old LTS version is based on an...
> Since the 6.c version is improved well into the 6.d releases, a good solution for this would be to provide rakudo-level switch that would "switch-off" 6.d features and make...
@duncand That worked for Swift because there was no exiting code base to maintain compatibility with. We do have that base which already relies on `6.c`/`6.d`. I'm not a big...
Use of full year would be a good option but apparently it will result in confusion with Rakudo versioning.