🦋 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.
Geth rakudo: MasterDuke17++ created pull request #5844:
Some random attribute access consistency changes		 01:40
ab5tract nine: ah, I see that the evals in that test are now evaling into the same package. I guess this was broken previously? Or else this has been failing for a long time without my noticing :( 05:51
Since I'm using `is-run`, I'm really surprised to see ths behavior 05:54
nine ab5tract: even if you leave just one of the is-runs it fails. I'd say it's because that warning code just doesn't know about revision-gated at all. It just sees 3 completely identical signatures 06:48
Geth rakudo/bootstrap-rakuast: 8 commits pushed by (Stefan Seifert)++ 06:57
ab5tract Intriguing… I’m a bit out of the coding vibe at the moment but I will try to take a look. Unfortunately there have been some other holes in the current implementation of the trait 08:13
It doesn’t do well on targets that are invoked heavily during bootstrapping, for instance
08:15 [Tux] left 08:18 [Tux] joined 09:26 finanalyst joined
ab5tract nine: that test file runs perfectly fine in base, so it seems to point more towards a bug in the RakuAST frontend? 11:41
nine Well that's what I said :) 11:51
ab5tract: I even posted the specific RakuAST commit that caused the failure: irclogs.raku.org/raku-dev/2025-04-07.html#14:15 11:52
ab5tract Yeah, got it 12:03
I have an easy mode patch in progress
It just skips this exception check if the proto has a required revision set 12:04
But I could also make it a bit more robust… maybe I’ll do that
hmm, that's going to require a bit more thinking than I want to do right now 12:16
I'll push the easy win version 12:17
nine cool
Geth rakudo/main: 304581eb3c | ab5tract++ | src/Raku/ast/code.rakumod
RakuAST: Fix failing revision gating tests

The RakuAST frontend now ignores revision gated protos and their dispatchees when deciding whether to throw an exception for multiple candidates of the same signature.
... (5 more lines)		 12:31
ab5tract just realizes he didn't run the full test suite(s) before pushing 12:32
but I can't see how it could harm anything (famous last words)
nine Looks quite safe indeed 12:33
ab5tract nine: I notice that a fair amount of the remaining tests from t/ are related to macros 12:38
are we going to take the time to "finalize" macros, to whatever degree that they need to move out of experimental? or just implement against the current tests and move on? 12:39
12:42 JimmyZhuo joined
nine ab5tract: as I understood it there's no intention of implementing support for the macros that these tests are covering. After all the point of RakuAST has mostly been to enable proper AST based macros. 12:47
ab5tract right, got it
nine So these tests should just be skipped. I'm actually surprised that they aren't already 12:48
ab5tract I've been assuming they are an "aftermarket add-on"
If we skip those, we boost the stats big time. Corporate says Go for it!
alas, I'm not savvy enough with the test harness stuff to know how to skip 12:55
nine docs.raku.org/type/Test#sub_skip 12:56
Or rather docs.raku.org/type/Test#sub_skip-rest 12:57
Geth rakudo/skip-exp-macro-tests: d8aed405d6 | ab5tract++ | 6 files
Skip experimental macro implementation tests
 13:26
rakudo: ab5tract++ created pull request #5846:
Skip experimental macro implementation tests
ab5tract plan :skip-all seems even more appropriate
however I get issues with the harness: 'Parse errors: No plan found in TAP output' 13:27
Geth rakudo/skip-exp-macro-tests: 80f51f199d | ab5tract++ | 6 files
Skip experimental macro implementation tests
 13:29
ab5tract if we changed the extension to .rakutest.skip ... ?
nine I don't think you need done-testing if you have a plan and the docs tell you to remove it 13:30
Geth rakudo/skip-exp-macro-tests: b8c62d96a9 | ab5tract++ | 12 files
Rename files instead
 13:31
ab5tract nine: yeah, I was already removing them as you wrote that :) 13:32
I was just poking around because it feels like this is a problem at the harness level
nine I guess there would still be compilation errors even with a skip-all 13:33
ab5tract indeed
but renaming works :)
nine Oh, a BEGIN plan :skip-all would have as well 13:41
ab5tract there we go 13:44
this is all in a PR for a reason :)
nine: hmm, it doesnt seem to work that way here.. 13:46
nine In what way does it fail?
> RAKUDO_RAKUAST=1 make t/13-experimental/macros-opaque-ast.rakutest 13:48
'/usr/bin/perl' -I'/home/nine/rakudo.main/tools/lib' -I'/home/nine/rakudo.main/3rdparty/nqp-configure/lib' t/harness5 --moar --fudge --keep-exit-code --verbosity=1 t/13-experimental/macros-opaque-ast.rakutest
skipped: NYI
Files=1, Tests=0, 1 wallclock secs ( 0.01 usr 0.00 sys + 0.16 cusr 0.02 csys = 0.19 CPU)
ab5tract as mentioned, `Parse errors: No plan found in TAP output`
nine +BEGIN plan :skip-all('NYI');
ab5tract I'm running make test and not seeing any changes
nine I don't see any BEGIN in the PR 13:49
14:02 JimmyZhuo left
ab5tract I didn't push it because it doesn't seem to work :) 14:18
it's easy enough to try locally, for now the .skip extension in the current PR is the only one I've gotten to work 14:19
nine Also means I can't look at the code. What does it say when you run in manually instead of through the harness?
ab5tract `Some exceptions were thrown in END blocks:` 14:20
`X::Multi::NoMatch: Cannot resolve caller Numeric(Pair:D: ); none of these signatures matches:`
Ah, I think I see the problem 14:23
> ./rakudo-m -Ilib t/13-experimental/macros.rakutest 14:25
1..skip-allTrueRakuAST macros supercede the macros described in these tests
===SORRY!=== Error while compiling t/13-experimental/macros.rakutest
Yeah, that's all the time I can put into it today, unfortunately 14:27
At least we got the revision gated stuff sorted
Geth rakudo/main: fd7d18088c | (Stefan Seifert)++ | 8 files
RakuAST: skip macro tests if running on RakuAST

There are no plans to implement the kind of macros described in these tests given that RakuAST's reason for existing is to provide a way to proper AST based macros.		 14:45
nine ab5tract: can you give this ^^^ a try? It....just works :D
japhb nine: Misspelled supersede :-) 14:49
nine I thought it looks fishy but I trusted that native speaker I copied it from :D
japhb Nah, we native speakers are lazier and more typo-prone. ;-) 14:50
[Coke] donaldh: there is a #raku-doc btw 14:52
16:46 finanalyst left 18:01 sena_kun joined 18:03 sena_kun left 18:04 sena_kun joined 18:06 sena_kun left 18:07 sena_kun joined 19:02 finanalyst joined 19:49 lizmat_ left 19:50 lizmat joined
donaldh thanks [Coke]++ 21:59
[Coke] thanks for the PR! 22:03
donaldh The #raku-doc channel is not well advertised, raku.org/community/ only mentions #raku 22:06
22:14 sena_kun left 22:19 donaldh_ joined
[Coke] releasable6: next 22:20
releasable6 [Coke], Next release in ≈9 days and ≈20 hours. 2 blockers. 233 out of 233 commits logged
[Coke], Details: gist.github.com/26b4ab63c8d7dd76be...1ac73dee70
[Coke] doesn't advertise this channel, either. :) 22:21
I think the thought is get folks to raku, and invite them elsewhere if appropriate. 22:22
22:22 donaldh_ left
jdv why do they need advert? 22:22
[Coke] but also a PR to the raku.org repo also welcome. ;)
I don't think we want to advert raku-dev, it helps to have a little privacy by obscurity. 22:23
jdv i mean anyone new makes sense in raku and can move on from there. nice to keep traffic more focused maybe. 22:24
[Coke] agreed 22:44

Powered by Cro and the Raku® Programming Language.

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

Thank you!