🦋 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.
lizmat m: dd Foo::Bar::Baz # vrurg shouldn't that complain about Bar missing in Foo? 09:32
evalable6 (exit code 1) Could not find symbol '&Baz' in 'GLOBAL::Foo::Bar'
in block <unit> at /tmp/FKq9zJJZlu line 1
nemokosch m: dd Foo::Bar::Baz:: 09:36
evalable6 (exit code 1) Could not find symbol '&Baz' in 'GLOBAL::Foo::Bar'
in block <unit> at /tmp/D9_VRgpYfC line 1
Raku eval Exit code: 1 Could not find symbol '&Baz' in 'GLOBAL::Foo::Bar' in block <unit> at main.raku line 1
nemokosch m: dd Foo::Bar::Baz::HowMuch
evalable6 (exit code 1) Could not find symbol '&HowMuch' in 'GLOBAL::Foo::Bar::Baz'
in block <unit> at /tmp/BOBXya27jz line 1
Raku eval Exit code: 1 Could not find symbol '&HowMuch' in 'GLOBAL::Foo::Bar::Baz' in block <unit> at main.raku line 1
nemokosch some autovivification magic probably 🤔
ab5tract m: dd Foo::Bar::Baz; dd Foo::Bar 10:00
evalable6 (exit code 1) Could not find symbol '&Baz' in 'GLOBAL::Foo::Bar'
in block <unit> at /tmp/DV2x4oodeH line 1
ab5tract So if I’m reading that right, the other namespaces get vivified… 10:02
lizmat m: try Foo::Bar::Baz; dd Foo::Bar 10:04
evalable6 (exit code 1) Could not find symbol '&Bar' in 'GLOBAL::Foo'
in block <unit> at /tmp/__IJzn2Fez line 1
ab5tract m: Q| dd Foo::Bar::Baz; dd Foo::Bar |.AST.EVAL.say 10:05
evalable6 (exit code 1) Could not find symbol '&Baz' in 'GLOBAL::Foo::Bar'
in block <unit> at /tmp/vltbidGMbi line 1
ab5tract ah, so the try seems to short-circuit early, but it still vivifies.. 10:06
Geth rakudo/main: a3bbb380f7 | (Elizabeth Mattijsen)++ | 2 files
RakuAST: the (s|w)orry-ad-hoc methods were removed

Sadly this was not detected earlier as the roast tests only check for dying, not why the code died.
This is a preliminary fix: a better way to convey worries / sorries from HLL code is needed.
11:44
lizmat m: try Foo::Bar::Baz; dd Foo::.keys 11:46
evalable6 (exit code 1) 4===SORRY!4=== Error while compiling /tmp/GPhM3NCuTn
Undeclared name:
Foo used at line 1
lizmat m: package Foo { }; try Foo::Bar::Baz; dd Foo::.keys
evalable6 ("Bar",).Seq
lizmat indeed autoviv
nemokosch this is among those things... 12:04
Geth Trait-IO/main: cdf074c111 | (Márton Polgár)++ (committed using GitHub Web editor) | .github/workflows/test.yml
Renovated workflow
14:26
vrurg lizmat: With regard to pseudostashes, I was raising a question on wether Foo::<Bar> must be a Failure when Bar is missing. But it never got discussed. Otherwise my point is that yes, it better complain earlier. 14:30
nemokosch great 14:32
vrurg But pseudos is a run-time (mostly) logic. I don't remember all the details about what the compiler does when resolves long names.
nemokosch rakudo.org killed all the CI workflows