🦋 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.
00:00 reportable6 left 00:02 reportable6 joined
MasterDuke nine: huh, thanks. will attempt that 02:29
hm. so i added `has int $!p5isms;` and `nqp::bindattr_i($obj, int, '$!p5isms', $p5isms ?? 1 !! 0);` to RakuAST::Call::Name and then `p5isms => $*LANG.pragma('p5isms')` to all the places (i think) a RakuAST::Call::Name is created in src/Raku/Actions.nqp and rakudo builds, but i get `P6opaque: no such attribute '$!p5isms' on type int in a 03:18
RakuAST::Call::Name when trying to bind a value` when running `RAKUDO_RAKUAST=1 raku -e 'use isms <Perl5>; say'`
nevermind, `nqp::bindattr_i($obj, int, '$!p5isms', $p5isms ?? 1 !! 0);` should be `nqp::bindattr_i($obj, RakuAST::Call::Name, '$!p5isms', $p5isms ?? 1 !! 0);` 03:26
06:00 reportable6 left, reportable6 joined 07:18 reportable6 left, evalable6 left, nativecallable6 left, linkable6 left, greppable6 left, bisectable6 left, releasable6 left, shareable6 left, notable6 left, sourceable6 left, quotable6 left, coverable6 left, unicodable6 left, tellable6 left, benchable6 left, statisfiable6 left, reportable6 joined, greppable6 joined, evalable6 joined, bisectable6 joined 07:19 quotable6 joined, unicodable6 joined, coverable6 joined 07:20 tellable6 joined, notable6 joined, statisfiable6 joined, releasable6 joined, nativecallable6 joined 07:21 linkable6 joined, sourceable6 joined, shareable6 joined, benchable6 joined
nine lizmat: how early do you need core.c? 07:48
08:01 kjp left, kjp joined
Geth rakudo/main: 134418bd16 | (Stefan Seifert)++ | src/Raku/Grammar.nqp
RakuAST: fix regression in BEGIN time EVAL processing

Commit a7571cb482847267c176455e9d1b6680c0511a4c removed the old POD implementation from the grammar, but also removed an unrelated line leading to the regression.
08:19 sena_kun joined 08:45 ab5tract joined 08:50 [TuxCM] left 08:51 [TuxCM] joined
lizmat nine++ 09:22
nine: *before* any code is encountered 09:23
during parsing
09:26 [TuxCM] left 09:30 [TuxCM] joined
Geth rakudo/main: 2dd66bcb85 | (Stefan Seifert)++ | 2 files
RakuAST: load CORE.c setting early for POD parsing

Parsing of POD needs classes defined in the CORE.c setting, so load it early and unconditionally. Any other setting will be loaded on top of that anyway.
nine lizmat: you're not out of the water yet. $*CU.pod-content.push($_.value.make-legacy-pod); will fail because there's no $*CU yet 09:31
lizmat nine: well, that's temporary anyway
it will need to create the legacy pod at CHECK time anyway 09:32
otherwise you won't be able to create custom RakuAST::Doc::Block nodes
09:34 ab5tract left, ab5tract joined
nine I'll leave that in your capable hands :) 09:41
And another broken spectest: throws-like { EVAL 'module MY;' } 09:48
It's only coincidence that we throw the expected expection before realizing that the "unit" is missing
09:49 [TuxCM] left
lizmat m: say␤=head1 FOO␤$=pod 09:52
camelia ===SORRY!===
Argument to "say" seems to be malformed
at <tmp>:1
------> say⏏<EOL>
Other potential difficulties:
Unsupported use of bare "say". In Raku please use: .say if you meant
to call it as a method on $_, or u…
nine m: unit module MY;
camelia ===SORRY!=== Error while compiling <tmp>
Cannot use pseudo package MY in package name
at <tmp>:1
------> unit module MY⏏;
expecting any of:
generic role
nine m: package Foo { module MY { } }
camelia ===SORRY!=== Error while compiling <tmp>
Cannot use pseudo package MY in package name
at <tmp>:1
------> package Foo { module MY⏏ { } }
expecting any of:
generic role
nine m: module Foo::MY { }
camelia ( no output )
lizmat MEH 09:53
m: say␤=head1 FOO␤␤$=pod
camelia [Pod::Heading{:level("1")}
lizmat TIL that you can have pod blocks in the middle of a statement
nine: did you know that ? 09:54
nine is a total POD newb
lizmat was as well
it's because pod blocks are basically the same as whitespace 09:55
10:10 [TuxCM] joined
Geth rakudo/main: b29e108487 | (Elizabeth Mattijsen)++ | src/Raku/Actions.nqp
RakuAST: reorganize Actions.statement a bit

Move the common code to the end of the method, for readability, but mostly to allow common statement actions to be done in one place. Also add some comments for clarity.
rakudo/main: aedeadf988 | (Stefan Seifert)++ | src/Raku/ast/name.rakumod
RakuAST: treat COMPILING as pseudo-package

COMPILING seems to be a reserved name and should be prohibited for declarations as pseudo-package, even though it's not actually implemented as such.
rakudo/main: 8b462b40a6 | (Stefan Seifert)++ | 4 files
RakuAST: prohibit using pseudo-package names in declarations
11:16 ab5tract left 12:00 reportable6 left 12:02 reportable6 joined
[TuxCM] github.com/rakudo/rakudo/issues/2483 extended with my yesterday findings 12:17
12:27 sena_kun left, lucs_ joined 12:38 lucs left 12:40 sena_kun joined 15:11 codesections joined 15:27 coleman left 15:39 coleman joined 15:40 codesections left 17:08 linkable6 left, evalable6 left 17:10 linkable6 joined 17:11 evalable6 joined
lizmat nine: ok, so I have the rakudoc blocks being added to the statement lists 17:44
however, it looks like they don't have their PERFORM-CHECK methods getting called
m: use v6.*; dd RakuAST::StatementList ~~ RakuAST::CheckTime 17:46
camelia Bool::False
lizmat meh
nine Are those blocks RakuAST::CheckTime? 17:55
lizmat the RakuAST::Doc::Blocks are 17:56
think I found it 17:57
18:00 reportable6 left 18:01 reportable6 joined
nine What was it? 18:02
lizmat yup, StatementList.visit-children was explicitely ignoring RakuAST::Doc::Blocks
nine Oh, yes, that can't be good. 18:03
18:31 codesections joined
lizmat codesections o/ 18:32
apparently we have spectests for pod inside code 18:37
inside a statement
apparently, having pod inside a { } intended to be a hash, now codegens as a block
also: having t/spec/S26-documentation/07b-tables.t pass until now, was a false positive 18:38
18:38 Altai-man joined
lizmat it only contains 4 dies-ok tests, and one of them doesn't die anymore 18:38
nine: re the block / hash test, any idea where I should look for that? 18:40
18:41 sena_kun left 18:49 codesections left
lizmat I'm inclined to push even though tests are +1 -1 18:56
with the note that the passing of S02-lexical-conventions/pod-in-multi-line-exprs.t before was a false positive 18:57
nine: ^^ ok with that ?
19:06 codesections joined 19:09 [TuxCM] left 19:24 [TuxCM] joined
nine lizmat: block-or-hash in src/Raku/ast/code.rakumod 19:48
19:49 codesections left 19:50 codesections joined 20:07 codesections left
nine If the test previously passing was just a false positive, "regressing" it is ok, I'd say 20:09
20:31 [TuxCM] left, [TuxCM] joined
vrurg I wonder, if a BOOTHash corruption is the primary suspect of a problem, is there a way to track it down somehow? Worst case, it's a memory corruption, but could be something else. 21:17
21:29 [TuxCM] left 21:31 [TuxCM] joined
Geth rakudo/main: 2bd735225e | (Elizabeth Mattijsen)++ | 6 files
RakuAST: RakuDoc blocks now interpreted correctly

Legacy pod blocks are now correctly created in $=pod from RakuAST objects, by moving the creation of the legace pod objects from the grammar to the CHECK time phase.
In the grammar, RakuDoc blocks are first stored in a dynamic array ... (9 more lines)
lizmat 794!
*phew*! 21:55
22:31 linkable6 left, evalable6 left 22:33 evalable6 joined, linkable6 joined 23:13 Altai-man left 23:34 [TuxCM] left 23:48 [TuxCM] joined 23:57 djinni` left