releasable6 Next release in ≈2 days and ≈11 hours. 3 blockers. Please log your changes in the ChangeLog: github.com/rakudo/rakudo/wiki/ChangeLog-Draft 07:00
Xliff Hello. I'm getting a P6M merge error that has me scratching my head. Golf here: repl.it/@Xliff/LovingMassiveVendors#C.pm6 07:43
Is this worth a bug?
sena_kun releasable6, status 07:45
releasable6 sena_kun, Next release in ≈2 days and ≈11 hours. 3 blockers. Changelog for this release was not started yet
sena_kun, Details: gist.github.com/98b4e6079926d69250...9bbe14770a
Geth rakudo/rakuast: 64b5c005d6 | (Jonathan Worthington)++ | 7 files
Implement application of traits to routine decls
 10:12
rakudo/rakuast: 90204bdde1 | (Elizabeth Mattijsen)++ | src/Raku/ast/code.rakumod
The /ast files are NQP bodies

They don't know about callsame!		 10:25
lizmat Xliff: our implies exporting, does it not ? 10:27
tellable6 lizmat, I'll pass your message to Xliff
lizmat hmmm... it does not 10:28
.tell Xliff have you tried "unit module A; our %RAW-DEFS; %RAW-DEFS<a> = 1" ? 10:30
tellable6 lizmat, I'll pass your message to Xliff
lizmat .tell Xliff confirmed wonkiness there, definitely worth an issue I'd say, if there isn't one for it already 10:38
tellable6 lizmat, I'll pass your message to Xliff
Geth rakudo/rakuast: 8ad47bc5de | (Jonathan Worthington)++ | 3 files
Add routine `return` handler and return type check
 10:47
Geth rakudo/rakuast: 0109545887 | (Elizabeth Mattijsen)++ | src/Raku/ast/call.rakumod
Use the same logic in DEPARSE as below
 11:40
rakudo/rakuast: 9668639c7d | (Elizabeth Mattijsen)++ | src/Raku/ast/literals.rakumod
DEPARSE should call .raku, not Str
rakudo/rakuast: 4413281851 | (Elizabeth Mattijsen)++ | t/12-rakuast/literals.t
Add some DEPARSE tests

To give jnthn an idea on how that would look. To be reverted if
  jnthn does not like. :-)
Geth roast: 382068506c | (Elizabeth Mattijsen)++ | S02-types/capture.t
Make test less sensitive to actual Capture.raku format
 12:37
rakudo: lizmat++ created pull request #3921:
De-huffmanize Capture.raku		 12:43
Geth rakudo/rakuast: 8209834524 | (Elizabeth Mattijsen)++ | t/12-rakuast/literals.t
Rework RakuAST::xxxLiteral tests

Introduces ast-ok to test whether EVALling an AST gives the expected result, as well as deparsing the given AST and (string) EVALling that gives the same result.
ast-ok name up for bikeshedding.		 13:50
Xliff . 13:52
tellable6 2020-09-17T10:27:41Z #raku-dev <lizmat> Xliff: our implies exporting, does it not ?
2020-09-17T10:30:37Z #raku-dev <lizmat> Xliff have you tried "unit module A; our %RAW-DEFS; %RAW-DEFS<a> = 1" ?
2020-09-17T10:38:16Z #raku-dev <lizmat> Xliff confirmed wonkiness there, definitely worth an issue I'd say, if there isn't one for it already
Xliff lizmat: Well... no. 'our' is more a visibility thing. 13:54
lizmat Xliff: yeah, realized that later :-)
Xliff Ah. See that, now. :)
Did you catch the golf?
lizmat: Can you declare a package of the same name across multiple compunits? 13:57
Put differently: Does Raku support the concept of partials?
lizmat I think in Raku that is implemented with the concept of roles
a compunit can export a role, and a class can consume multiple roles 13:58
Xliff Now that I think about it... I think augment would be a better match.
I'm thinking more of a collection spread across multiple compunits.
a "package Abracadabra { }" can be defined in many compunits, but another compunit can't use both definitions, can it? 13:59
lizmat not adaik 14:00
*afaik
Xliff OK.
I think Raku really needs a namespace concept. 14:01
lizmat I think it has ?
Xliff Which is more like a package, but parts of it can be scattered across multiple compunits.
You "use" the parts you need. That might be a nightmare to implement, though.
lizmat I think it could be done with an "is mergeable" trait on the class 14:03
if you're interested in getting stuff together from different files
and they're not conflicting, you can already do that by *not* specifying any package 14:04
Xliff And that is what I am doing.
The problem is when I try and "use" two compunits that have an our-scoped variable with the same shortname
s/variable/symbol/
Xliff goes to bug. 14:05
github.com/rakudo/rakudo/issues/3922 14:14
[Coke] Xliff: rectivied == rectified? 14:16
Xliff [Coke]: LOL -- yes 14:25
Edited. Thanks.
Addendum to R34922 15:08
repl.it/@Xliff/SwelteringEarnestSpof#D.pm6
Er.
R#3922 15:09
linkable6 R#3922 [open]: github.com/rakudo/rakudo/issues/3922 P6M Merging error when using non-packaged our-scoped variables with a prefix.
Geth rakudo/rakuast: 4 commits pushed by (Elizabeth Mattijsen)++ 21:02
lizmat .tell tbrowder food for thought: perlhacks.com/2020/09/blogging-for-perl/ 21:28
tellable6 lizmat, I'll pass your message to tbrowder
timotimo "there's more than one way to blog it" reminds me of the POSSE idea from the indieweb community 21:29
tbrowder lizmat: i agree with dave, but i'm looking for an easy-to-use public blog site (not wordpress) and so far i haven't found one i like. maybe i'll run my own like codesections, but i'd rather not unless forced to. 22:53
tellable6 2020-09-17T21:28:06Z #raku-dev <lizmat> tbrowder food for thought: perlhacks.com/2020/09/blogging-for-perl/
tbrowder lizmat: btw, how do you search for raku tweets for the weekly? 22:55

Powered by Cro and the Raku® Programming Language.

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

Thank you!