rakudo
problem-solving
rakudo | problem-solving | |
---|---|---|
55 | 21 | |
1,697 | 69 | |
0.1% | - | |
9.9 | 0.0 | |
about 24 hours ago | 5 months ago | |
Raku | ||
Artistic License 2.0 | Artistic License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
rakudo
-
Stability
Fix IO::Path::parent #4795: merged 2022-02-19 Add more IO::Path::parent tests #801: merged 2022-02-19 Change parent to always just remove the last element #4800: merged 2022-02-26 Change .parent behavior to "stupid" resolving #802: merged 2022-02-26
-
Moving printf formats forward
This then became the Formatter class. And since this was a completely new feature, it only became available for use by opting into the 6.e.PREVIEW language version. And then it went largely unnoticed and uncared for the next 1.5 year. As clearly the time wasn't right for it yet.
-
Shaking the RakuAST Tree
The intended audience are those people willing to be early adopters of these exciting new features in the Raku Programming Language. The examples in this blog post will work in the next release of the Rakudo compiler (probably 2023.06), but are now already available in the bleeding edge version.
-
So why is there RakuAST in the first place?
If you really want to look at this, you can find the code in src/Perl6/Grammar.nqp, src/Perl6/Actions.nqp and src/Perl6/World.nqp.
-
A practical example of RakuAST
If you find this very interesting, you probably want to read the RakuAST README. And the actual source code of the RakuAST classes can be found in the same directory. And if you're really feeling adventurous and you have the Rakudo repository checked out, you can have a look at the generated NQP code in gen/moar/ast.nqp.
-
RakuAST for Early Adopters
Yes, it would. But until there was RakuAST, that was virtually impossible to do because there was no proper API for building ASTs. Nor was there an interface to execute those ASTs. And now that there is RakuAST, it is actually possible to do this. And there is actually already an implementation of that idea in the new Formatter class. Although this is definitely not intended as an entry point into grokking RakuAST.
-
What explains this difference in behavior?
I have opened one. https://github.com/rakudo/rakudo/issues/5205.
-
Why isn't sign() defined for Complex numbers?
Will Coleda has made a Pull Request
-
Building Rakudo on JVM backend fails: guarantee(requested_word_size <= chunklevel::MAX_CHUNK_WORD_SIZE) failed: Requested size too large (561049) - max allowed size per allocation is 524288
There's an issue pertaining to this. This is something I'd like to resolve, but I'm unsure on how to better debug this to see if it really is the deserialization of a setting file triggering it. JDK 11 should at least be capable of building Rakudo, but being an experimental backend people don't always align with MoarVM immediately, I can't make any guarantees about tests. You may be disappointed in its performance at the moment.
-
Resources and advice
(NB. While the PL is just a toy (and just a tiny bit of the toy too), the tech is actually industrial strength, used to power the production Raku compiler, which is written in Raku using its grammar construct. Starting easy doesn't mean you can't go far. Quite the opposite in fact -- you can go as far as you want.)
problem-solving
-
Stability
Supply blocks may reorder flow of execution #364: solved Deadlock in supply / whenever chain #5141: fixed Simplify Supply / whenever processing order #5158: superseeded Fix rare deadlocks during supply setup #5202: merged 2023-11-24 Switch Supply.zip to a watermark approach (https://github.com/rakudo/rakudo/pull/5211rework) #5211: merged 2023-03-09 Test supply setup with a blocking recursion #833: merged 2023-11-24
-
Why isn't sign() defined for Complex numbers?
I'm more leaning towards the former. you could open an issue at https://github.com/Raku/problem-solving/issues so that it won't get forgotten.
-
Nowadays, self-hosting your compiler just doesn't demonstrate much of anything. It takes a lot more than a compiler to prove anything meaningful about your language. Time spent on self-hosting is mostly just time wasted. It mainly suggests you were not really serious.
A bunch of people really good at bikeshedding took over the conversation and by the time they were done, the language looked nothing like Perl and they decided to rename it after the butterfly.
-
Support arbitrary git URLs as Raku module dependencies.
Now, there are security issues with the "p6c" ecosystem, as one can change the contents of a module without a version bump (aka without anybody noticing). So the plan is that the "p6c" ecosystem will be disabled by default.
- Preparing the Raku Ecosystem for the Future - Problem Solving Issue
-
Grammatical Actions: further thoughts on cooperative Raku grammars | CodeSections
Either way, I posted the other day a problem solving issue on the topic. I think we should start looking into ways to properly supporting the mixed grammars, be it a trait-like thing (you've basically made a trait without being a trait), a token (like mine) or some other specialized regex syntax.
-
Perl Turns 34 Today
There was no admitting to themselves.
There was the personal realization that the two factions in what was then the Perl community, would never see eye to eye on what the language called "Perl 6" was. And that all of my efforts of reconciliation, such as the Perl Reunification Summit http://blogs.perl.org/users/gabor_szabo/2013/02/perl-reunifi... had been in vain.
Which lead me to open an issue https://github.com/Raku/problem-solving/issues/81 which in the end resulted in the rename to the Raku Programming Language https://raku.org .
-
Whatever same argument multiple times
The CALLER:: initiates a symbol lookup in the caller. The MY:: limits that lookup to just the caller's lexpad. This is confusing. cf Particular scopes of PseudoStash'es are not clear #294.
-
Annotations for the Complete Type (or Data::Record's Identity Crisis)
Over time, most of the features that were a selling point for Data::Record have been rendered silly. Namely, the idea of a Tuple and Dict in core has been tossed about since writing, and the introduction of type inference for lists into core leaves most of the collections as which Data::Record is defined (Data::Record::Tuple, Data::Record::List, Data::Record::Map) with the odd edge case to cover, of which I don't feel it does a very good job of in its current release's state.
-
What's everyone working on this week? [2021, week 26]
On my patrol of the wrongly named Discord channel #raku-beginners (I'm a Raku beginner since 2008, so this name is redundant), I spotted once again the question of iteration on nested Hashes and Arrays. Since the HyperWhatever wasn't taken yet (not everyone wants the colon) I wrote a proposal. I'm not sure if my nqp-foo is sufficient but I might give it a shot anyway. Unless lizmat wants to micro-optimise code that has not been written yet.
What are some alternatives?
instaparse
perl5 - 🐪 The Perl programming language
coalton - Coalton is an efficient, statically typed functional programming language that supercharges Common Lisp.
raku-website - A website for the Raku programming language
enso - Hybrid visual and textual functional programming.
ra-Data-Record - Record types!
CSSTidy-cro - Experimental Online CSS Tidy Facility (* Under Construction *)
roast - 🦋 Raku test suite
metacpan-web - Web interface for MetaCPAN
langs
chroma - A general purpose syntax highlighter in pure Go