Re: Announce: Rakudo Star Release 2017.07

[Todd Chester]

On 07/25/2017 12:30 AM, Elizabeth Mattijsen wrote:

What do you mean by “the full Rakudo” ?  Rakudo Star is the Rakudo compiler 
release with a set of useful modules added (“batteries included”).



https://rakudo.perl6.org/downloads/star/

 vs

https://rakudo.perl6.org/downloads/rakudo/


And to add insult Fedora only supports Rakudo

Re: Announce: Rakudo Star Release 2017.07

[raiph mellor]

TL;DR Imo, one of Perl 6's notable strengths is its approach to its
specification. Imo companies will love it. I can see it becoming a
primary tool for driving P6 forward in just the right way.



Steve has already answered with the short version of some of what I
say below, and I agree with what you (Darren) said in your reply to
him. So perhaps this is more for ToddAndMargo or other readers.

>From the start in 2000, Larry intended that the P6 project would
distinguish between various distinct notions of "specification":

* An evolving set of English documents that would be used to guide
compiler developers attempting to write a compiler that implements
that "specification". For the last few years P6 project leaders have
been calling these "Design Documents". The latest/last versions of
these are stored at design.perl6.org. They are now largely an
historical footnote -- calling these or any other English language
documents a "specification" was explicitly deprecated some years ago.

* An evolving set of English documents that would be used to guide end
users attempting to understand or write P6 code. Aka end user
documentation. The latest version of this is stored at doc.perl6.org.
Contributors can draw insight from the design documents (as per
previous bullet point) but are supposed to focus on the only remaining
specification (as per the next bullet point).

* An evolving Executable specification that emerges from that effort.
A compiler **must** match **100%** of this executable specification if
the compiler is to be officially allowed to claim it implements that
specification. This is what the 6.c specification is and what the 6.d
specification will be.

* The 6.c specification is stored at
https://github.com/perl6/roast/tree/6.c (Maybe we should change the
description from "Perl 6 test suite" to "Perl 6 language
specification".) There's also a 6.c errata at
https://github.com/perl6/roast/tree/6.c-errata which, aiui, is what
the monthly Rakudo releases target.

So, anything you read in English, like "doesn't yet implement macros"
is... written in English and is not part of a Perl 6 language
specification, per contemporary P6 usage of the word "specification".

> So I think it is reasonable for Rakudo to actually implement ALL of 6.c 
> before too long, that it would catch up, and otherwise the intent is that 
> Rakudo would be leading on things that eventually become 6.d etc later.

Aiui Rakudo's HEAD implemented all of 6.c (on at least one platform)
as of December 25th 2015 and each subsequent monthly release has as
well. (Well, actually, all of 6.c.errata.)

In principle this is an excellent foundation for manageable (in tech
and business senses), systematic, community driven, compiler dev
mediated, language stability, backwards compatibility, and evolution.

If someone (or some company) wants to drive the language forward, then
they work with the community to propose changes to the test suite for
6.d or some later 6.* version. These changes test that the particular
features they want are working.

Community members can do things like attaching a time-limited
incentive for compiler devs to alter the compiler to pass some
particular set of new tests.

Indeed, I imagine it would be fairly easy to set up a flow of direct
micro-funding of whatever a given community participant considers more
important to them. If it's backwards compatibility, then write tests
that ensure that backwards compatibility if they haven't already been
written and/or add incentives to currently failing/skipped tests. A
similar approach applies for those wanting more test coverage of
existing features, or new features.

--
raiph

On Tue, Jul 25, 2017 at 11:23 AM, Darren Duncan  wrote:
> There's a key difference however.
>
> While programming languages continue to evolve, the expectation is that a
> production-complete Rakudo would always be a functional superset (or equal
> to) the Perl 6 language specification which is current at the time.
>
> So I think it is reasonable for Rakudo to actually implement ALL of 6.c
> before too long, that it would catch up, and otherwise the intent is that
> Rakudo would be leading on things that eventually become 6.d etc later.
>
> The original question would be more accurately phrased, "Any idea when
> Rakudo will release implementing the full Perl 6.c?"
>
> -- Darren Duncan
>
> On 2017-07-25 1:02 AM, Elizabeth Mattijsen wrote:
>>
>> If that is the question, the answer is: the junction of “never" and “now".
>> Which would also be the answer for Pumpking Perl 5, or any other programming
>> language like ever.  Because as long as people are using it, a programming
>> language will evolve.  Much like any human endeavour I would say.
>>
>>> On 25 Jul 2017, at 09:42, Andrew Kirkpatrick  wrote:
>>>
>>> I assume the meaning is, roughly when is the implementation expected
>>> to cover the entire spec?
>>>
>>> Answering this is probably an exercise in 

Re: Announce: Rakudo Star Release 2017.07

[Darren Duncan]

On 2017-07-25 10:05 AM, Brandon Allbery wrote:

On Tue, Jul 25, 2017 at 11:45 AM, Darren Duncan wrote:

However I assume it is the 3 bullet points that the release announcement
highlights: advanced macros, non-blocking I/O, bits of Synopsis 9 and 11.
The fact the announcement highlights these implies they are part of the
creators' definition of "complete".

The "advanced macros" part, at least, probably needs to go away: a large part of
the problem is that nobody actually knows what "advanced macros" for Perl 6
should do, or even look like. (See for example masak's 007, which is a
playground for macros to try to get a handle on the question of what they ought
to be/do.)


I agree with your point and should further say that I think at this point the 
Rakudo announcements should stop naming that features are missing except where 
they are key show-stopper-for-some features.


Don't highlight the fact that some things are missing.  That would always be the 
case.


At this point things are complete enough that most people wouldn't even notice 
things were missing if they weren't told and it doesn't affect them.


In my opinion, non-blocking I/O is the only thing on the list that deserves to 
be highlighted, that and the warnings about the level of JVM support.


-- Darren Duncan

Re: Announce: Rakudo Star Release 2017.07

[Brandon Allbery]

On Tue, Jul 25, 2017 at 11:45 AM, Darren Duncan 
wrote:

> However I assume it is the 3 bullet points that the release announcement
> highlights: advanced macros, non-blocking I/O, bits of Synopsis 9 and 11.
> The fact the announcement highlights these implies they are part of the
> creators' definition of "complete".


The "advanced macros" part, at least, probably needs to go away: a large
part of the problem is that nobody actually knows what "advanced macros"
for Perl 6 should do, or even look like. (See for example masak's 007,
which is a playground for macros to try to get a handle on the question of
what they ought to be/do.)

-- 
brandon s allbery kf8nh   sine nomine associates
allber...@gmail.com  ballb...@sinenomine.net
unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net

Re: Announce: Rakudo Star Release 2017.07

[Darren Duncan]

On 2017-07-25 8:32 AM, Steve Mynott wrote:

On 25 July 2017 at 16:23, Darren Duncan  wrote:

There's a key difference however.

While programming languages continue to evolve, the expectation is that a
production-complete Rakudo would always be a functional superset (or equal
to) the Perl 6 language specification which is current at the time.


The Perl 6 language specification is the test suite. So if the test
suite passes then it's complete! Which is of course a tautology.


So by that definition, "complete" is that the arbitrary subset of the spec that 
an implementation chooses to do passes the tests for those parts, and the rest 
of the tests skip rather than fail.



So I think it is reasonable for Rakudo to actually implement ALL of 6.c
before too long, that it would catch up, and otherwise the intent is that
Rakudo would be leading on things that eventually become 6.d etc later.


Which missing parts are you concerned about?


I'm not personally concerned about any parts at this time.

It is ToddAndMargo that is concerned about it, who asked the question.

However I assume it is the 3 bullet points that the release announcement 
highlights: advanced macros, non-blocking I/O, bits of Synopsis 9 and 11.  The 
fact the announcement highlights these implies they are part of the creators' 
definition of "complete".


-- Darren Duncan

Re: Announce: Rakudo Star Release 2017.07

[Steve Mynott]

On 25 July 2017 at 16:33, Stephen Wilcoxon  wrote:
> I don't see anything in the notes (though I may have missed it) about JVM.
> I thought the plan was to get JVM functional again (though likely still
> lagging MoarVM feature support) with the 2017.07 release?

There are comments in the README

"Please note that this release of Rakudo Star is *not* fully functional with the
JVM backend from the Rakudo compiler.  Use the JVM backend only if you are
trying to help with fixing JVM support (which is best done upstream with the
monthly Rakudo release).  This is a known issue and it's not worth reporting
JVM failures as bugs unless you have patches."

The last time I tried it (and this was a while ago) I was able to
build with JVM and run simple (dozen line) programs OK.  But complex
programs like zef didn't work and so installing modules wasn't
possible.

S

Re: Announce: Rakudo Star Release 2017.07

[Stephen Wilcoxon]

I don't see anything in the notes (though I may have missed it) about JVM.
I thought the plan was to get JVM functional again (though likely still
lagging MoarVM feature support) with the 2017.07 release?

Perl 6 on MoarVM is definitely interesting but, to me at least, the single
biggest practical impact or Rakudo was that it is (or was) supposed to run
on JVM (allowing usage of any other libs on JVM and, probably more
importantly, making it easier to convince management to allow using it).

On Tue, Jul 25, 2017 at 10:23 AM, Darren Duncan 
wrote:

> There's a key difference however.
>
> While programming languages continue to evolve, the expectation is that a
> production-complete Rakudo would always be a functional superset (or equal
> to) the Perl 6 language specification which is current at the time.
>
> So I think it is reasonable for Rakudo to actually implement ALL of 6.c
> before too long, that it would catch up, and otherwise the intent is that
> Rakudo would be leading on things that eventually become 6.d etc later.
>
> The original question would be more accurately phrased, "Any idea when
> Rakudo will release implementing the full Perl 6.c?"
>
> -- Darren Duncan
>
> On 2017-07-25 1:02 AM, Elizabeth Mattijsen wrote:
>
>> If that is the question, the answer is: the junction of “never" and
>> “now".  Which would also be the answer for Pumpking Perl 5, or any other
>> programming language like ever.  Because as long as people are using it, a
>> programming language will evolve.  Much like any human endeavour I would
>> say.
>>
>> On 25 Jul 2017, at 09:42, Andrew Kirkpatrick  wrote:
>>>
>>> I assume the meaning is, roughly when is the implementation expected
>>> to cover the entire spec?
>>>
>>> Answering this is probably an exercise in futility, because its up to
>>> the community and not anyone in particular.
>>>
>>> On 25 July 2017 at 17:00, Elizabeth Mattijsen  wrote:
>>>
>> [snip]
>
>
>
> Any idea when the full Rakudo will be released?
>

 What do you mean by “the full Rakudo” ?  Rakudo Star is the Rakudo
 compiler release with a set of useful modules added (“batteries included”).

 So you could argue that Rakudo doesn’t get fuller than with Rakudo Star!

>>>
>>

Re: Announce: Rakudo Star Release 2017.07

[Steve Mynott]

On 25 July 2017 at 16:23, Darren Duncan  wrote:
> There's a key difference however.
>
> While programming languages continue to evolve, the expectation is that a
> production-complete Rakudo would always be a functional superset (or equal
> to) the Perl 6 language specification which is current at the time.

The Perl 6 language specification is the test suite. So if the test
suite passes then it's complete! Which is of course a tautology.

> So I think it is reasonable for Rakudo to actually implement ALL of 6.c
> before too long, that it would catch up, and otherwise the intent is that
> Rakudo would be leading on things that eventually become 6.d etc later.

Which missing parts are you concerned about?

> The original question would be more accurately phrased, "Any idea when
> Rakudo will release implementing the full Perl 6.c?"

It's a volunteer effort so this happens whenever someone who cares
enough about missing parts and who has the time and skills to
implement does it.

S

Re: Announce: Rakudo Star Release 2017.07

[Darren Duncan]

There's a key difference however.

While programming languages continue to evolve, the expectation is that a 
production-complete Rakudo would always be a functional superset (or equal to) 
the Perl 6 language specification which is current at the time.


So I think it is reasonable for Rakudo to actually implement ALL of 6.c before 
too long, that it would catch up, and otherwise the intent is that Rakudo would 
be leading on things that eventually become 6.d etc later.


The original question would be more accurately phrased, "Any idea when Rakudo 
will release implementing the full Perl 6.c?"


-- Darren Duncan

On 2017-07-25 1:02 AM, Elizabeth Mattijsen wrote:

If that is the question, the answer is: the junction of “never" and “now".  
Which would also be the answer for Pumpking Perl 5, or any other programming language 
like ever.  Because as long as people are using it, a programming language will evolve.  
Much like any human endeavour I would say.


On 25 Jul 2017, at 09:42, Andrew Kirkpatrick  wrote:

I assume the meaning is, roughly when is the implementation expected
to cover the entire spec?

Answering this is probably an exercise in futility, because its up to
the community and not anyone in particular.

On 25 July 2017 at 17:00, Elizabeth Mattijsen  wrote:

[snip]



Any idea when the full Rakudo will be released?


What do you mean by “the full Rakudo” ?  Rakudo Star is the Rakudo compiler 
release with a set of useful modules added (“batteries included”).

So you could argue that Rakudo doesn’t get fuller than with Rakudo Star!

Re: Announce: Rakudo Star Release 2017.07

[Timo Paulssen]

Were there any failures before the "Building NQP ..." step? Somehow the
moarvm that's packaged with the rakudo star didn't end up getting
installed into your .local/bin, so you're getting the previous version,
which - unsurprisingly - isn't new enough for current NQP and Rakudo.

Re: Announce: Rakudo Star Release 2017.07

[Mark Carter]

Attempted build on Arch Linux:

perl Configure.pl --prefix=$HOME/.local --backend=moar --gen-moar --gen-moar

Resulting in:

Building NQP ...
/usr/bin/perl Configure.pl --prefix=/home/mcarter/.local --backends=moar 
--make-install

Creating tools/build/install-jvm-runner.pl ...

===SORRY!===
Found /home/mcarter/.local/bin/moar version 2017.04-53-g66c6dda, which is too 
old. Wanted at least 2017.07

No suitable MoarVM (moar executable) found using the --prefix
(You can get a MoarVM built automatically with --gen-moar.)

Command failed (status 65280): /usr/bin/perl Configure.pl 
--prefix=/home/mcarter/.local --backends=moar --make-install

Re: Announce: Rakudo Star Release 2017.07

[Elizabeth Mattijsen]

If that is the question, the answer is: the junction of “never" and “now".  
Which would also be the answer for Pumpking Perl 5, or any other programming 
language like ever.  Because as long as people are using it, a programming 
language will evolve.  Much like any human endeavour I would say.

> On 25 Jul 2017, at 09:42, Andrew Kirkpatrick  wrote:
> 
> I assume the meaning is, roughly when is the implementation expected
> to cover the entire spec?
> 
> Answering this is probably an exercise in futility, because its up to
> the community and not anyone in particular.
> 
> On 25 July 2017 at 17:00, Elizabeth Mattijsen  wrote:
>>> On 25 Jul 2017, at 05:57, ToddAndMargo  wrote:
>>> On 07/24/2017 11:40 AM, Steve Mynott wrote:
 A useful and usable production distribution of Perl 6
 On behalf of the Rakudo and Perl 6 development teams, I'm pleased to
 announce the July 2017 release of "Rakudo Star", a useful and usable
 production distribution of Perl 6. The tarball for the July 2017
 release is available from https://rakudo.perl6.org/downloads/star/.
 Binaries for macOS and Windows (64 bit) are also available.
 This is the eighth post-Christmas (production) release of Rakudo Star
 and implements Perl v6.c. It comes with support for the MoarVM backend
 (all module tests pass on supported platforms).
 IMPORTANT: "panda" is to be removed very shortly since it is
 deprecated. Please use "zef" instead.
 Currently, Star is on a quarterly release cycle and 2017.10 (October)
 will follow later this year.
 Please note that this release of Rakudo Star is not fully functional
 with the JVM backend from the Rakudo compiler. Please use the MoarVM
 backend only.
 In the Perl 6 world, we make a distinction between the language ("Perl
 6") and specific implementations of the language such as "Rakudo
 Perl".
 This Star release includes release 2017.07 of the Rakudo Perl 6
 compiler, version 2017.07 MoarVM, plus various modules, documentation,
 and other resources collected from the Perl 6 community.
 Note this Star release contains NQP version 2017.07-9-gc0abee7 rather
 than the release NQP 2017.07 in order to fix the --ll-exception
 command line flag.
 The Rakudo compiler changes since the last Rakudo Star release of
 2017.01 are now listed in "2017.05.md", "2017.06.md" and "2017.07.md"
 under the "rakudo/docs/announce" directory of the source distribution.
 Notable changes in modules shipped with Rakudo Star:
 + DBIish: Doc and CI updates
 + doc: Too many to list. p6doc fixed.
 + grammar-debugger: Works again now.
 + p6-io-string: New dep for doc.
 + p6-native-resources: Removed since deprecated and not used by linenoise.
 + panda: Officially deprecate panda in favour of zef.
 + perl6-Test-When: New dep for perl6-pod-to-bigpage.
 + perl6-lwp-simple: Fix breakage due to rakudo encoding refactor.
 + tap-harness6: Replaces deprecated tap-harness6-prove6.
 + zef: Too many to list.
 There are some key features of Perl 6 that Rakudo Star does not yet
 handle appropriately, although they will appear in upcoming releases.
 Some of the not-quite-there features include:
 + advanced macros
 + non-blocking I/O (in progress)
 + some bits of Synopsis 9 and 11
 There is an online resource at http://perl6.org/compilers/features
 that lists the known implemented and missing features of Rakudo's
 backends and other Perl 6 implementations.
 In many places we've tried to make Rakudo smart enough to inform the
 programmer that a given feature isn't implemented, but there are many
 that we've missed. Bug reports about missing and broken features are
 welcomed at rakudo...@perl.org.
 See https://perl6.org/ for links to much more information about Perl
 6, including documentation, example code, tutorials, presentations,
 reference materials, design documents, and other supporting resources.
 Some Perl 6 tutorials are available under the "docs" directory in the
 release tarball.
 The development team thanks all of the contributors and sponsors for
 making Rakudo Star possible. If you would like to contribute, see
 http://rakudo.org/how-to-help, ask on the perl6-compi...@perl.org
 mailing list, or join us on IRC #perl6 on freenode.
>>> 
>>> 
>>> Any idea when the full Rakudo will be released?
>> 
>> What do you mean by “the full Rakudo” ?  Rakudo Star is the Rakudo compiler 
>> release with a set of useful modules added (“batteries included”).
>> 
>> So you could argue that Rakudo doesn’t get fuller than with Rakudo Star!

Re: Announce: Rakudo Star Release 2017.07

[Andrew Kirkpatrick]

I assume the meaning is, roughly when is the implementation expected
to cover the entire spec?

Answering this is probably an exercise in futility, because its up to
the community and not anyone in particular.

On 25 July 2017 at 17:00, Elizabeth Mattijsen  wrote:
>> On 25 Jul 2017, at 05:57, ToddAndMargo  wrote:
>> On 07/24/2017 11:40 AM, Steve Mynott wrote:
>>> A useful and usable production distribution of Perl 6
>>> On behalf of the Rakudo and Perl 6 development teams, I'm pleased to
>>> announce the July 2017 release of "Rakudo Star", a useful and usable
>>> production distribution of Perl 6. The tarball for the July 2017
>>> release is available from https://rakudo.perl6.org/downloads/star/.
>>> Binaries for macOS and Windows (64 bit) are also available.
>>> This is the eighth post-Christmas (production) release of Rakudo Star
>>> and implements Perl v6.c. It comes with support for the MoarVM backend
>>> (all module tests pass on supported platforms).
>>> IMPORTANT: "panda" is to be removed very shortly since it is
>>> deprecated. Please use "zef" instead.
>>> Currently, Star is on a quarterly release cycle and 2017.10 (October)
>>> will follow later this year.
>>> Please note that this release of Rakudo Star is not fully functional
>>> with the JVM backend from the Rakudo compiler. Please use the MoarVM
>>> backend only.
>>> In the Perl 6 world, we make a distinction between the language ("Perl
>>> 6") and specific implementations of the language such as "Rakudo
>>> Perl".
>>> This Star release includes release 2017.07 of the Rakudo Perl 6
>>> compiler, version 2017.07 MoarVM, plus various modules, documentation,
>>> and other resources collected from the Perl 6 community.
>>> Note this Star release contains NQP version 2017.07-9-gc0abee7 rather
>>> than the release NQP 2017.07 in order to fix the --ll-exception
>>> command line flag.
>>> The Rakudo compiler changes since the last Rakudo Star release of
>>> 2017.01 are now listed in "2017.05.md", "2017.06.md" and "2017.07.md"
>>> under the "rakudo/docs/announce" directory of the source distribution.
>>> Notable changes in modules shipped with Rakudo Star:
>>> + DBIish: Doc and CI updates
>>> + doc: Too many to list. p6doc fixed.
>>> + grammar-debugger: Works again now.
>>> + p6-io-string: New dep for doc.
>>> + p6-native-resources: Removed since deprecated and not used by linenoise.
>>> + panda: Officially deprecate panda in favour of zef.
>>> + perl6-Test-When: New dep for perl6-pod-to-bigpage.
>>> + perl6-lwp-simple: Fix breakage due to rakudo encoding refactor.
>>> + tap-harness6: Replaces deprecated tap-harness6-prove6.
>>> + zef: Too many to list.
>>> There are some key features of Perl 6 that Rakudo Star does not yet
>>> handle appropriately, although they will appear in upcoming releases.
>>> Some of the not-quite-there features include:
>>> + advanced macros
>>> + non-blocking I/O (in progress)
>>> + some bits of Synopsis 9 and 11
>>> There is an online resource at http://perl6.org/compilers/features
>>> that lists the known implemented and missing features of Rakudo's
>>> backends and other Perl 6 implementations.
>>> In many places we've tried to make Rakudo smart enough to inform the
>>> programmer that a given feature isn't implemented, but there are many
>>> that we've missed. Bug reports about missing and broken features are
>>> welcomed at rakudo...@perl.org.
>>> See https://perl6.org/ for links to much more information about Perl
>>> 6, including documentation, example code, tutorials, presentations,
>>> reference materials, design documents, and other supporting resources.
>>> Some Perl 6 tutorials are available under the "docs" directory in the
>>> release tarball.
>>> The development team thanks all of the contributors and sponsors for
>>> making Rakudo Star possible. If you would like to contribute, see
>>> http://rakudo.org/how-to-help, ask on the perl6-compi...@perl.org
>>> mailing list, or join us on IRC #perl6 on freenode.
>>
>>
>> Any idea when the full Rakudo will be released?
>
> What do you mean by “the full Rakudo” ?  Rakudo Star is the Rakudo compiler 
> release with a set of useful modules added (“batteries included”).
>
> So you could argue that Rakudo doesn’t get fuller than with Rakudo Star!

Re: Announce: Rakudo Star Release 2017.07

[Elizabeth Mattijsen]

> On 25 Jul 2017, at 05:57, ToddAndMargo  wrote:
> On 07/24/2017 11:40 AM, Steve Mynott wrote:
>> A useful and usable production distribution of Perl 6
>> On behalf of the Rakudo and Perl 6 development teams, I'm pleased to
>> announce the July 2017 release of "Rakudo Star", a useful and usable
>> production distribution of Perl 6. The tarball for the July 2017
>> release is available from https://rakudo.perl6.org/downloads/star/.
>> Binaries for macOS and Windows (64 bit) are also available.
>> This is the eighth post-Christmas (production) release of Rakudo Star
>> and implements Perl v6.c. It comes with support for the MoarVM backend
>> (all module tests pass on supported platforms).
>> IMPORTANT: "panda" is to be removed very shortly since it is
>> deprecated. Please use "zef" instead.
>> Currently, Star is on a quarterly release cycle and 2017.10 (October)
>> will follow later this year.
>> Please note that this release of Rakudo Star is not fully functional
>> with the JVM backend from the Rakudo compiler. Please use the MoarVM
>> backend only.
>> In the Perl 6 world, we make a distinction between the language ("Perl
>> 6") and specific implementations of the language such as "Rakudo
>> Perl".
>> This Star release includes release 2017.07 of the Rakudo Perl 6
>> compiler, version 2017.07 MoarVM, plus various modules, documentation,
>> and other resources collected from the Perl 6 community.
>> Note this Star release contains NQP version 2017.07-9-gc0abee7 rather
>> than the release NQP 2017.07 in order to fix the --ll-exception
>> command line flag.
>> The Rakudo compiler changes since the last Rakudo Star release of
>> 2017.01 are now listed in "2017.05.md", "2017.06.md" and "2017.07.md"
>> under the "rakudo/docs/announce" directory of the source distribution.
>> Notable changes in modules shipped with Rakudo Star:
>> + DBIish: Doc and CI updates
>> + doc: Too many to list. p6doc fixed.
>> + grammar-debugger: Works again now.
>> + p6-io-string: New dep for doc.
>> + p6-native-resources: Removed since deprecated and not used by linenoise.
>> + panda: Officially deprecate panda in favour of zef.
>> + perl6-Test-When: New dep for perl6-pod-to-bigpage.
>> + perl6-lwp-simple: Fix breakage due to rakudo encoding refactor.
>> + tap-harness6: Replaces deprecated tap-harness6-prove6.
>> + zef: Too many to list.
>> There are some key features of Perl 6 that Rakudo Star does not yet
>> handle appropriately, although they will appear in upcoming releases.
>> Some of the not-quite-there features include:
>> + advanced macros
>> + non-blocking I/O (in progress)
>> + some bits of Synopsis 9 and 11
>> There is an online resource at http://perl6.org/compilers/features
>> that lists the known implemented and missing features of Rakudo's
>> backends and other Perl 6 implementations.
>> In many places we've tried to make Rakudo smart enough to inform the
>> programmer that a given feature isn't implemented, but there are many
>> that we've missed. Bug reports about missing and broken features are
>> welcomed at rakudo...@perl.org.
>> See https://perl6.org/ for links to much more information about Perl
>> 6, including documentation, example code, tutorials, presentations,
>> reference materials, design documents, and other supporting resources.
>> Some Perl 6 tutorials are available under the "docs" directory in the
>> release tarball.
>> The development team thanks all of the contributors and sponsors for
>> making Rakudo Star possible. If you would like to contribute, see
>> http://rakudo.org/how-to-help, ask on the perl6-compi...@perl.org
>> mailing list, or join us on IRC #perl6 on freenode.
> 
> 
> Any idea when the full Rakudo will be released?

What do you mean by “the full Rakudo” ?  Rakudo Star is the Rakudo compiler 
release with a set of useful modules added (“batteries included”).

So you could argue that Rakudo doesn’t get fuller than with Rakudo Star!

Re: Announce: Rakudo Star Release 2017.07

[ToddAndMargo]

On 07/24/2017 11:40 AM, Steve Mynott wrote:

A useful and usable production distribution of Perl 6

On behalf of the Rakudo and Perl 6 development teams, I'm pleased to
announce the July 2017 release of "Rakudo Star", a useful and usable
production distribution of Perl 6. The tarball for the July 2017
release is available from https://rakudo.perl6.org/downloads/star/.

Binaries for macOS and Windows (64 bit) are also available.

This is the eighth post-Christmas (production) release of Rakudo Star
and implements Perl v6.c. It comes with support for the MoarVM backend
(all module tests pass on supported platforms).

IMPORTANT: "panda" is to be removed very shortly since it is
deprecated. Please use "zef" instead.

Currently, Star is on a quarterly release cycle and 2017.10 (October)
will follow later this year.

Please note that this release of Rakudo Star is not fully functional
with the JVM backend from the Rakudo compiler. Please use the MoarVM
backend only.

In the Perl 6 world, we make a distinction between the language ("Perl
6") and specific implementations of the language such as "Rakudo
Perl".

This Star release includes release 2017.07 of the Rakudo Perl 6
compiler, version 2017.07 MoarVM, plus various modules, documentation,
and other resources collected from the Perl 6 community.

Note this Star release contains NQP version 2017.07-9-gc0abee7 rather
than the release NQP 2017.07 in order to fix the --ll-exception
command line flag.

The Rakudo compiler changes since the last Rakudo Star release of
2017.01 are now listed in "2017.05.md", "2017.06.md" and "2017.07.md"
under the "rakudo/docs/announce" directory of the source distribution.

Notable changes in modules shipped with Rakudo Star:

+ DBIish: Doc and CI updates
+ doc: Too many to list. p6doc fixed.
+ grammar-debugger: Works again now.
+ p6-io-string: New dep for doc.
+ p6-native-resources: Removed since deprecated and not used by linenoise.
+ panda: Officially deprecate panda in favour of zef.
+ perl6-Test-When: New dep for perl6-pod-to-bigpage.
+ perl6-lwp-simple: Fix breakage due to rakudo encoding refactor.
+ tap-harness6: Replaces deprecated tap-harness6-prove6.
+ zef: Too many to list.

There are some key features of Perl 6 that Rakudo Star does not yet
handle appropriately, although they will appear in upcoming releases.
Some of the not-quite-there features include:

+ advanced macros
+ non-blocking I/O (in progress)
+ some bits of Synopsis 9 and 11

There is an online resource at http://perl6.org/compilers/features
that lists the known implemented and missing features of Rakudo's
backends and other Perl 6 implementations.

In many places we've tried to make Rakudo smart enough to inform the
programmer that a given feature isn't implemented, but there are many
that we've missed. Bug reports about missing and broken features are
welcomed at rakudo...@perl.org.

See https://perl6.org/ for links to much more information about Perl
6, including documentation, example code, tutorials, presentations,
reference materials, design documents, and other supporting resources.
Some Perl 6 tutorials are available under the "docs" directory in the
release tarball.

The development team thanks all of the contributors and sponsors for
making Rakudo Star possible. If you would like to contribute, see
http://rakudo.org/how-to-help, ask on the perl6-compi...@perl.org
mailing list, or join us on IRC #perl6 on freenode.





Any idea when the full Rakudo will be released?

Announce: Rakudo Star Release 2017.07

[Steve Mynott]

A useful and usable production distribution of Perl 6

On behalf of the Rakudo and Perl 6 development teams, I'm pleased to
announce the July 2017 release of "Rakudo Star", a useful and usable
production distribution of Perl 6. The tarball for the July 2017
release is available from https://rakudo.perl6.org/downloads/star/.

Binaries for macOS and Windows (64 bit) are also available.

This is the eighth post-Christmas (production) release of Rakudo Star
and implements Perl v6.c. It comes with support for the MoarVM backend
(all module tests pass on supported platforms).

IMPORTANT: "panda" is to be removed very shortly since it is
deprecated. Please use "zef" instead.

Currently, Star is on a quarterly release cycle and 2017.10 (October)
will follow later this year.

Please note that this release of Rakudo Star is not fully functional
with the JVM backend from the Rakudo compiler. Please use the MoarVM
backend only.

In the Perl 6 world, we make a distinction between the language ("Perl
6") and specific implementations of the language such as "Rakudo
Perl".

This Star release includes release 2017.07 of the Rakudo Perl 6
compiler, version 2017.07 MoarVM, plus various modules, documentation,
and other resources collected from the Perl 6 community.

Note this Star release contains NQP version 2017.07-9-gc0abee7 rather
than the release NQP 2017.07 in order to fix the --ll-exception
command line flag.

The Rakudo compiler changes since the last Rakudo Star release of
2017.01 are now listed in "2017.05.md", "2017.06.md" and "2017.07.md"
under the "rakudo/docs/announce" directory of the source distribution.

Notable changes in modules shipped with Rakudo Star:

+ DBIish: Doc and CI updates
+ doc: Too many to list. p6doc fixed.
+ grammar-debugger: Works again now.
+ p6-io-string: New dep for doc.
+ p6-native-resources: Removed since deprecated and not used by linenoise.
+ panda: Officially deprecate panda in favour of zef.
+ perl6-Test-When: New dep for perl6-pod-to-bigpage.
+ perl6-lwp-simple: Fix breakage due to rakudo encoding refactor.
+ tap-harness6: Replaces deprecated tap-harness6-prove6.
+ zef: Too many to list.

There are some key features of Perl 6 that Rakudo Star does not yet
handle appropriately, although they will appear in upcoming releases.
Some of the not-quite-there features include:

+ advanced macros
+ non-blocking I/O (in progress)
+ some bits of Synopsis 9 and 11

There is an online resource at http://perl6.org/compilers/features
that lists the known implemented and missing features of Rakudo's
backends and other Perl 6 implementations.

In many places we've tried to make Rakudo smart enough to inform the
programmer that a given feature isn't implemented, but there are many
that we've missed. Bug reports about missing and broken features are
welcomed at rakudo...@perl.org.

See https://perl6.org/ for links to much more information about Perl
6, including documentation, example code, tutorials, presentations,
reference materials, design documents, and other supporting resources.
Some Perl 6 tutorials are available under the "docs" directory in the
release tarball.

The development team thanks all of the contributors and sponsors for
making Rakudo Star possible. If you would like to contribute, see
http://rakudo.org/how-to-help, ask on the perl6-compi...@perl.org
mailing list, or join us on IRC #perl6 on freenode.


-- 
4096R/EA75174B Steve Mynott