Anton Oks

@lizmat @coke What do you think? Can I merge those quick&dirty additions to make clear it's a "Star" release, people use? That i.e. would help users to differentiate between the...

“Transferring issues” works for someone, who has proper permissions on both involved GitHub repos… as long as we have our repos and CI’s on this platform 😊 Nevertheless, from some...

> #raku-star on Libera.chat @lizmat - do you plan to "review" and / or comment on this pull? So, shall I therefore wait for your feedback here and/or now and...

> I would not be against modifying the raku version output. But I would be against modifying `src/Perl6/Compiler.nqp` for this. 1. because I don't like distributions to change source code...

> I don't like this. The rakudo itself is not different between star and plain. This change will add to the confusion if the raku(do) executable reports itself as star....

> No! That's not what I wanted to say! I believe there is a place for the Star bundle. That's also evident from the stable user base. Ok, thanks. And...

> As file name, I would suggest "SYNDICATION". Thanks for your suggestion. "SYNDICATION" somehow makes my brain spinning... haven't seen this kind of name for something like "enhanced release of...

> It can just be added to the code in Compiler.nqp. As NQP code, which would mean an nqp::open, nqp::read and an nqp::close. Since the reading would be done at...

> > It can just be added to the code in Compiler.nqp. As NQP code, which would mean an nqp::open, nqp::read and an nqp::close. Since the reading would be done...

> > As file name, I would suggest "SYNDICATION". > > Thanks for your suggestion. "SYNDICATION" somehow makes my brain spinning... haven't seen this kind of name for something like...