🦋 Welcome to the IRC channel of the core developers of the Raku Programming Language (raku.org #rakulang). This channel is logged for the purpose of history keeping about its development | evalbot usage: 'm: say 3;' or /msg camelia m: ... | Logs available at irclogs.raku.org/raku-dev/live.html | For MoarVM see #moarvm
Set by lizmat on 8 June 2022.
releasable6 Next release in ≈2 days and ≈11 hours. There are no known blockers. Please log your changes in the ChangeLog: github.com/rakudo/rakudo/wiki/ChangeLog-Draft 07:00
Geth rakudo/main: a46987933f | (Elizabeth Mattijsen)++ | 3 files
RakuAST: make =for foo and =foo grab trailing whitespace

Sometimes extra trailing whitespace can be significant for rendering rakudoc. But =for foo and =foo were only taking the first newline. This is now fixed, with necessary changes to legacy podification and the POC text rendering.		 09:56
Geth rakudo/main: af54c0b2ea | (Elizabeth Mattijsen)++ | 2 files
RakuAST: make =doc block deparsing closer to the bone

Now assumes the contents will always end with a newline, rather than inserting newlines itself. Also removes the extra leading newline which implies that any leading newlines in the source code before a rakudoc block will disappear in deparsing as it is not significant.		 10:25
Geth rakudo/main: 3139b6c05f | (Elizabeth Mattijsen)++ (committed using GitHub Web editor) | src/core.c/Any.pm6
Handle uncontainerized type objects as invocant to AT-POS better

If the invocant is a container, nothing changes. If the invocant is a type object, then look at the index. If the index is greater than 0, then Failure. Else consider the type object as a single element list, so return the invocant.		 10:50
Geth rakudo/main: 149dd88014 | (Elizabeth Mattijsen)++ | 4 files
Attempt #2 at introducing Iterator.is-monotonically-increasing

  - fixed stupid "already in use/consumed" error in Any.sort which
   would happen if the source iterator was *not* monotonically
   increasing (which is in like 99% of the cases)
  - made sure iterators that wrap other iterators, pass on the
   is-monotonically-increasing information
  - made sure that .sort with &cmp produces an iterator that
   has the "is-monotonically-increasing" flag set		 12:57
lizmat Nemokosch ^^ 12:58
Nemokosch sorry what was the goal of this again? 14:29
lizmat m: say (1..*).sort[^10) 14:31
camelia ===SORRY!=== Error while compiling <tmp>
Unable to parse expression in subscript; couldn't find final ']' (corresponding starter was at line 1)
at <tmp>:1
------> say (1..*).sort[^10⏏)
expecting any of:
statement e…
lizmat m: say (1..*).sort[^10]
camelia Cannot sort a lazy list
in block <unit> at <tmp> line 1
lizmat hmm
camelia stuck? 14:32
Nemokosch oh right
lizmat anyways, to make that work, because we know that 1..* is already sorted, so the .sort can be a. not bomb, and b. be a no-op
Nemokosch the "we know more about sorting a range than a random infinite sequence" topic
lizmat published a blog post again: dev.to/lizmat/rakuast-for-early-adopters-576n 16:09

Powered by Cro and the Raku® Programming Language.

Please report any issues / comments / feature requests as an issue on App::Raku::Log.

Thank you!