๐Ÿฆ‹ Welcome to Raku! raku.org/ | evalbot usage: 'p6: say 3;' or /msg camelia p6: ... | irclog: colabti.org/irclogger/irclogger_log/raku
Set by ChanServ on 14 October 2019.
00:35 finanalyst left
Geth_ ecosystem/bbkr-patch-1: 5b74a410cf | (Pawel Pabian)++ (committed using GitHub Web editor) | META.list
Added HomoGlypher - tool for handling similarly looking characters in strings.
00:43
ecosystem: bbkr++ created pull request #477:
Added HomoGlypher - tool for handling similarly looking characters in strings
00:44
01:17 sauvin_ is now known as sauvin 01:20 Altai-man_ joined 01:22 sena_kun left 01:26 TreyHarris left 01:39 TreyHarris joined 01:56 kalkin-- joined 01:59 kalkin- left 02:26 leont left 03:21 sena_kun joined 03:23 Altai-man_ left 04:23 bloatable6 left, bisectable6 left, sourceable6 left, greppable6 left, committable6 left, coverable6 left, shareable6 left, releasable6 left, reportable6 left, nativecallable6 left, squashable6 left, quotable6 left, unicodable6 left, notable6 left, statisfiable6 left, benchable6 left 04:24 shareable6 joined, nativecallable6 joined, squashable6 joined, committable6 joined 04:25 releasable6 joined, reportable6 joined, coverable6 joined, unicodable6 joined, notable6 joined 04:26 statisfiable6 joined, bloatable6 joined, sourceable6 joined, benchable6 joined, marcusr left, bisectable6 joined, quotable6 joined, greppable6 joined 04:29 cpan-raku left 04:31 cpan-raku joined, cpan-raku left, cpan-raku joined 05:20 Altai-man_ joined 05:23 sena_kun left
Xliff m: use NativeCall; BEGIN my $bit_type := uint64; class A is repr<CStruct> { has $bit_type $.a }; A.new( a => 42 ); A.gist.say 06:05
camelia 5===SORRY!5=== Error while compiling <tmp>
Two terms in a row
at <tmp>:1
------> 3class A is repr<CStruct> { has $bit_type7โ5 $.a }; A.new( a => 42 ); A.gist.say
expecting any of:
infix
infix stopper
โ€ฆ
Xliff m: use NativeCall; BEGIN constant bitType := uint64; class A is repr<CStruct> { has bitType $.a }; A.new( a => 42 ); A.gist.say
camelia (A)
Xliff m: use NativeCall; BEGIN constant bitType := uint64; class A is repr<CStruct> { has bitType $.a }; A.new( a => 42 ); A.a.say
camelia Cannot look up attributes in a A type object
in method a at <tmp> line 1
in block <unit> at <tmp> line 1
Xliff m: use NativeCall; BEGIN constant bitType := uint64; class A is repr<CStruct> { has bitType $.a }; A.new( a => 42 ); A.new.gist.say
camelia A.new(a => 0)
Xliff m: use NativeCall; BEGIN constant bitType := uint64; class A is repr<CStruct> { has bitType $.a; submethod BUILD (:$!a) {}; }; A.new( a => 42 ); A.new.gist.say 06:06
camelia Cannot unbox a type object (Any) to int.
in submethod BUILD at <tmp> line 1
in block <unit> at <tmp> line 1
Xliff m: use NativeCall; BEGIN constant bitType := uint64; class A is repr<CStruct> { has bitType $.a; submethod BUILD (:$a) { $!a = $a }; }; A.new( a => 42 ); A.new.gist.say
camelia Cannot unbox a type object (Any) to int.
in submethod BUILD at <tmp> line 1
in block <unit> at <tmp> line 1
Xliff m: use NativeCall; BEGIN constant bitType := uint64; class A is repr<CStruct> { has bitType $.a; submethod BUILD (:$a) { say $a }; }; A.new( a => 42 ); A.new.gist.say 06:07
camelia 42
(Any)
A.new(a => 0)
Xliff m: use NativeCall; BEGIN constant bitType := uint64; class A is repr<CStruct> { has bitType $.a; submethod BUILD (:$a) { say $a }; }; A.new(); A.new.gist.say
camelia (Any)
(Any)
A.new(a => 0)
Xliff m: use NativeCall; BEGIN constant bitType := uint64; class A is repr<CStruct> { has bitType $.a; submethod BUILD (:$a) { say $a }; }; A.new( a => 42); A.new.gist.say
camelia 42
(Any)
A.new(a => 0)
Xliff m: use NativeCall; BEGIN constant bitType := uint64; class A is repr<CStruct> { has bitType $.a; submethod BUILD (:$a) { say $a }; $!a = $a }; A.new( a => 42 ); A.new.gist.say 06:08
camelia 5===SORRY!5=== Error while compiling <tmp>
Variable $!a used where no 'self' is available
at <tmp>:1
------> 3a; submethod BUILD (:$a) { say $a }; $!a7โ5 = $a }; A.new( a => 42 ); A.new.gist.sa
ยป
Xliff m: use NativeCall; BEGIN constant bitType := uint64; class A is repr<CStruct> { has bitType $.a; submethod BUILD (:$a) { say $a; $!a = $a }; A.new( a => 42 ); A.new.gist.say
camelia 5===SORRY!5=== Error while compiling <tmp>
Missing block
at <tmp>:1
------> 3= $a }; A.new( a => 42 ); A.new.gist.say7โ5<EOL>
expecting any of:
statement end
statement modifier
statement modifier looโ€ฆ
Xliff m: use NativeCall; BEGIN constant bitType := uint64; class A is repr<CStruct> { has bitType $.a; submethod BUILD (:$a) { say $a; $!a = $a }; }; A.new( a => 42 ); A.new.gist.say
camelia 42
Cannot unbox a type object (Any) to int.
in submethod BUILD at <tmp> line 1
in block <unit> at <tmp> line 1

(Any)
Xliff m: use NativeCall; BEGIN constant bitType := uint64; class A is repr<CStruct> { has bitType $.a; submethod BUILD (:$a) { say $a; }; }; A.new( a => 42 ); A.new.gist.say
camelia 42
(Any)
A.new(a => 0)
Xliff m: use NativeCall; BEGIN constant bitType := uint64; class A is repr<CStruct> { has bitType $.a; submethod BUILD (:$a) { say $a if $a.defined }; }; A.new( a => 42 ); A.new.gist.say 06:09
camelia 42
A.new(a => 0)
Xliff m: use NativeCall; BEGIN constant bitType := uint64; class A is repr<CStruct> { has bitType $.a; submethod BUILD (:$!a) {}; }; A.new( a => 42 ).gist.say
camelia A.new(a => 42)
06:17 marcusr joined 06:20 marcusr left 06:21 marcusr joined
Geth_ ecosystem: 5b74a410cf | (Pawel Pabian)++ (committed using GitHub Web editor) | META.list
Added HomoGlypher - tool for handling similarly looking characters in strings.
06:47
ecosystem: f34a860868 | (Jonathan Stowe)++ (committed using GitHub Web editor) | META.list
Merge pull request #477 from perl6/bbkr-patch-1

Added HomoGlypher - tool for handling similarly looking characters in strings
07:01 rindolf joined 07:21 sena_kun joined 07:23 Altai-man_ left 07:32 rindolf left 07:39 hacktor left 08:03 mid_laptop joined
Geth_ doc: f788c9dedc | (JJ Merelo)++ | doc/Language/terms.pod6
Merges code and deindents

Since there's no difference now after 6.d. Refs #2632. Also eliminates a reference to 6.d.PREVIEW refs #2687
08:12
doc: 1d223c2fc5 | (JJ Merelo)++ | doc/Type/Complex.pod6
Fixes example

And also adds example of fixed complex exponentiation, refs #2632
08:26 rindolf joined 08:33 kensanata joined 08:40 mid_laptop left 08:41 mid_laptop joined
Geth_ advent: nige123++ created pull request #46:
Update schedule
08:47
08:53 kensanata left 08:58 rindolf left 08:59 kensanata joined 09:02 kensanata left
Geth_ advent: 885757425d | (Nigel Hamilton)++ (committed using GitHub Web editor) | raku-advent-2020/schedule
Update schedule
09:04
advent: 0b650f611e | (Elizabeth Mattijsen)++ (committed using GitHub Web editor) | raku-advent-2020/schedule
Merge pull request #46 from nige123/patch-4

Update schedule
09:20 kensanata joined, kensanata left, Altai-man_ joined 09:21 rindolf joined, kensanata joined 09:23 sena_kun left 09:24 chloekek joined
chloekek . 09:24
Xliff chleokek: ,
Don't mind me. I'm sleepless...and not in Seattle! 09:25
chloekek p6: use europe; say 1,2 + 3,4;
camelia ===SORRY!===
Could not find europe at line 1 in:
inst#/home/camelia/.perl6
inst#/home/camelia/rakudo-m-inst-1/share/perl6/site
inst#/home/camelia/rakudo-m-inst-1/share/perl6/vendor
inst#/home/camelia/rakudo-m-inst-1/share/perโ€ฆ
chloekek Hmm, no comma for decimal point. But I can write my string literals in Dutch! 09:26
p6: say โ€žHallo, wereld!โ€œ
camelia Hallo, wereld!
Xliff Try doing that in C#
Progress is slow...but at least it is progress. 09:27
chloekek I once wrote a C# parser in Haskell and I called the parsing function parseC# because you can put # at the end of an identifier.
Xliff Until you can do Cโ™ฏ ... it's a crude imitator. 09:28
chloekek p6: sub parse-Cโ™ฏ { }
camelia 5===SORRY!5=== Error while compiling <tmp>
Missing block
at <tmp>:1
------> 3sub parse-C7โ5โ™ฏ { }
expecting any of:
new name to be defined
09:29 kensanata left
Xliff *gasp* 09:29
I'm shocked!
09:29 kensanata joined
Xliff m: parse-C# { } 09:29
camelia 5===SORRY!5=== Error while compiling <tmp>
Undeclared routine:
parse-C used at line 1
Xliff m: parse-Cโ™ฏ { }
camelia 5===SORRY!5=== Error while compiling <tmp>
Bogus postfix
at <tmp>:1
------> 3parse-C7โ5โ™ฏ { }
expecting any of:
infix
infix stopper
statement end
statement modifier
statement modโ€ฆ
chloekek p6: sub postfix:<โ™ฏ>($x) { $x }; sub parse-C { 123 }; say parse-Cโ™ฏ
camelia 123
Xliff Not marked as a letter or a number in the parser. 09:30
m: parse-Cฮฑ { }
camelia 5===SORRY!5=== Error while compiling <tmp>
Undeclared routine:
parse-Cฮฑ used at line 1
chloekek Itโ€™s a musical symbol.
Xliff m: sub parse-Cฮฑ { }
camelia ( no output )
chloekek Alpha is a letter so it is allowed.
Xliff Yes. That was what I was getting at.
chloekek I think musical symbols are in the category Math Symbol 09:31
Xliff Yeah. OK. That's why it wouldn't work.
chloekek Some are in Other Symbol it seems.
Lol there is QUARTER NOTE but also MUSICAL SYMBOL QUARTER NOTE 09:32
p6: say โ€˜โ™ฉโ€™ eq โ€˜๐…˜๐…ฅโ€™
camelia False
09:33 kensanata left, kensanata joined
Xliff Aannd....back to more sleepless I go. 09:34
09:34 kensanata left
Xliff I have to wake up for work in 4 hours. :( 09:34
chloekek p6: .say for (0 .. 0x10FFFF).map(*.chr).grep(*.uniname.starts-with(โ€˜MUSICAL SYMBOL โ€™)) 09:36
camelia ๐„€
๐„
๐„‚
๐„ƒ
๐„„
๐„…
๐„†
๐„‡
๐„ˆ
๐„‰
๐„Š
๐„‹
๐„Œ
๐„
๐„Ž
๐„
๐„
๐„‘
๐„’
๐„“
๐„”
๐„•
๐„–
๐„—
๐„˜
๐„™
๐„š
๐„›
๐„œ
๐„
๐„ž
๐„Ÿ
๐„ 
๐„ก
๐„ข
๐„ฃโ€ฆ
chloekek p6: say (0 .. 0x10FFFF).map(*.chr).grep(*.uniname.starts-with(โ€˜MUSICAL SYMBOL โ€™)).elems 09:38
camelia 231
lizmat afk& 09:40
09:41 kensanata joined 09:48 vividsnow joined
cpan-raku New module released to CPAN! Crypt::SodiumPasswordHash (0.0.1) by 03JSTOWE 10:01
chloekek Where is the parser for nqp? 10:04
moritz in the nqp repo, src/NQP/Grammar.nqp 10:06
chloekek Ah cool. Thanks. 10:10
cpan-raku New module released to CPAN! Crypt::AnyPasswordHash (0.0.3) by 03JSTOWE 10:16
10:30 Xliff left, Xliff_ joined 10:37 pilne left 10:40 xinming left 10:41 xinming joined 10:58 kensanata left 11:09 wamba joined 11:11 finanalyst joined, xinming left, xinming joined 11:21 sena_kun joined 11:23 Altai-man_ left 11:37 kensanata joined 11:59 stoned75 joined 12:09 leont joined
lizmat PSA: the last Rakudo Weekly of 2019 will be published tomorrow morning 12:13
12:19 stoned75 left
chloekek p6: BEGIN { f; }; sub f { } 12:37
camelia 5===SORRY!5=== Error while compiling <tmp>
Undeclared routine:
f used at line 1
12:37 finanalyst left
chloekek p6: sub f { }; BEGIN { f; } 12:37
camelia ( no output )
chloekek p6: sub f { g; }; sub g { } 12:38
camelia ( no output )
chloekek p6: sub f { g; };
camelia 5===SORRY!5=== Error while compiling <tmp>
Undeclared routine:
g used at line 1
chloekek This is interesting; compiling a subroutine definition sees subroutines defined later.
BEGIN obviously cannot. What would happen if g were an infix operator instead? 12:40
That seems to work as well. Then, how is precedence done? Are subroutine bodies not parsed immediately?
Oh, actually it doesnโ€™t work with infix operators. 12:41
cpan-raku New module released to CPAN! Method::Also (0.0.5) by 03ELIZABETH 12:55
New module released to CPAN! RedX::HashedPassword (0.0.4) by 03JSTOWE 13:03
13:20 Altai-man_ joined
leont Does the ยซtoken element:<foo>ยป syntax have a particular name? 13:21
13:23 sena_kun left 13:36 kalkin-- is now known as kalkin- 13:47 mahmudov joined 13:49 mid_laptop left
chloekek leont: assuming you mean token element:sym<foo>, theyโ€™re called proto regexes in the manual. 13:56
14:00 wamba left 14:15 lucasb joined
cpan-raku New module released to CPAN! Crypt::AnyPasswordHash (0.0.4) by 03JSTOWE 14:35
14:48 mensvaga joined 14:56 wamba joined 15:21 sena_kun joined 15:23 Altai-man_ left 15:28 kensanata left
cpan-raku New module released to CPAN! MeCab (0.0.17) by 03TITSUKI 15:36
New module released to CPAN! MeCab (0.0.16) by 03TITSUKI
15:51 johnjohn101 left 15:58 dotdotdot left, rindolf left
cpan-raku New module released to CPAN! Algorithm::LibSVM (0.0.11) by 03TITSUKI 15:59
16:01 rindolf joined 16:02 dotdotdot joined
cpan-raku New module released to CPAN! Chart::Gnuplot (0.0.16) by 03TITSUKI 16:07
16:10 jmerelo joined
cpan-raku New module released to CPAN! Random::Choice (0.0.7) by 03TITSUKI 16:14
16:15 rindolf left 16:41 chloekek left 17:07 rindolf joined 17:21 Altai-man_ joined 17:23 sena_kun left 17:41 chloekek joined 17:46 stoned75 joined, unclechu left, matiaslina left, BlackChaosNL[m] left, CIAvash left, uzl[m] left, Demos[m] left, AlexDaniel` left, rba[m] left 17:47 Nasrudin left 18:01 kensanata joined 18:02 CIAvash joined 18:12 stoned75 left
chloekek Is it possible for a grammar/regex to modify the input string at some point during parsing, so that a different string will be used to continue parsing? 18:19
e.g. โ€˜fooโ€™ โ€˜(โ€™ <expr>ย โ€™)โ€™ { my $new-string = EVAL $<expr>; <.continue-with($new-string ~ $current-remainder)> } 18:22
rindolf chloekek: hi - no idea here 18:24
kalkin- m: say "1".succ; say "ยน".succ; say "โ’ˆ".succ 18:25
camelia 2
ยน
โ’ˆ
kalkin- why it does not work with ยน & โ’ˆ? 18:26
[Coke] ยน is only a superscript where it makes sense. 18:28
er.
only a *power*
m: say 1 eq ยน 18:29
camelia True
[Coke] m: say 1 === ยน
camelia True
[Coke] m: say 1 =:= ยน
camelia True
kalkin- ok, but the second one is a 1 with dot, this should be incremented
[Coke] m: say 1 == ยน # oops, not eq!
camelia True
[Coke] m: dd โ’ˆ 18:30
camelia 1
[Coke] m: say โ’ˆ === 1
kalkin- m: say ("โ’ˆ".ord +1).chr
camelia True
โ’‰
[Coke] yup, that seems buggy.
I misread your question, btw. :) 18:31
might fall out of digit vs. number handling.
but at first glance, seems suprising.
18:32 kensanata left 18:35 lucasb left, mahmudov left 18:41 BlackChaosNL[m] joined, unclechu joined, AlexDaniel` joined, EuAndreh[m] joined, rba[m] joined, Demos[m] joined, uzl[m] joined, matiaslina joined, Nasrudin joined 18:47 mahmudov joined 18:50 hacktor joined 18:56 mensvaga left
kalkin- so once again, is it a bug or a feature? Should I open a github issue for that? 18:57
jmerelo say "โ’ˆ ".uniprops 18:59
evalable6 (No Zs)
tellable6 2019-12-22T14:47:23Z #raku <tbrowder> jmerelo i can't tell if my advent post is scheduled properly--the bloody calendar display seems to have changed on me! please help!
hey jmerelo, you have a message: gist.github.com/df277fb78c251e4b0b...aea4d33e45
jmerelo say "1".uniprops
evalable6 (Nd)
jmerelo say "โ’ˆ ".uniprops
evalable6 (No Zs)
jmerelo say "ยน".uniprops 19:00
evalable6 (No)
jmerelo kalkin-: different unicode properties. I would say that's a feature.
kalkin-: surprisingly enough, digits and numbers are not exactly the same 19:01
kalkin- say "a".succ; say "โ‘ "succ
m: say "a".succ; say "โ‘ "succ
camelia 5===SORRY!5=== Error while compiling <tmp>
Two terms in a row
at <tmp>:1
------> 3say "a".succ; say "โ‘ "7โ5succ
expecting any of:
infix
infix stopper
postfix
statement end
statemโ€ฆ
jmerelo .tell chloekek that's amazing. I'll check it out (I saw it on twitter, too)
tellable6 jmerelo, I'll pass your message to chloekek
jmerelo .tell tbrowder I'll check
tellable6 jmerelo, I'll pass your message to tbrowder
kalkin- m: say "a".succ; say "โ‘ "succ;
camelia 5===SORRY!5=== Error while compiling <tmp>
Two terms in a row
at <tmp>:1
------> 3say "a".succ; say "โ‘ "7โ5succ;
expecting any of:
infix
infix stopper
postfix
statement end
stateโ€ฆ
kalkin- m: say "a".succ; say "โ‘ ".succ;
camelia b
โ‘ก
jmerelo .tell tbrowder it's been published anyway, so we're good.
tellable6 jmerelo, I'll pass your message to tbrowder
kalkin- m: say "โ‘ ".uniprops 19:02
camelia (No)
kalkin- jmerelo: according to your theory โ‘  should not work
jmerelo kalkin-: it's a number
that means you can't join it with other "Nos" to create numbers with several digits. 19:03
kalkin- m: say "ยน".uniprops; say "ยน".succ
camelia (No)
ยน
jmerelo And you can compare it numerically
say 1 == ยน
evalable6 True
jmerelo But it's not exactly the same
say 1 === ยน
kalkin- but "ยน" is also a No and succ doesn't work on it
evalable6 True
jmerelo Ah, OK. I didn't know that was the precise issue. 19:04
Might be a bug, but I'd look at the set of properties before
kalkin- to sum it up: why is 1, ยน, โ’ˆ and โ‘  all handled differently? 19:05
jmerelo: what set properties do you mean?
jmerelo Well, 1 is Nd, and the rest are No, for starters. But your point is that succ works in all of them but ยน 19:06
Also, โ’ˆ is actually a combination of two codepoints. It might evaluate dynamically to 1, but again, it's not the same.
kalkin- and โ’ˆ is also not supported 19:07
DIGIT ONE FULL STOP (if you don't see it clearly)
19:07 wildtrees joined
jmerelo uniprop just returns the general category, but it might have more categories. 19:08
Unicode is a whole world.
kalkin- so shall i open a GitHub issue? 19:10
jmerelo And No needn't have a successor, I think. It might have, but then...
kalkin-: it will always help clarify any ambiguity, of course, in case there's one 19:11
And f*ck
There's nothing scheduled for today.
.seen kaiepi 19:13
tellable6 jmerelo, I saw kaiepi 2019-12-22T11:05:09Z in #raku: <Kaiepi> i was expecting it to work like assigning to `my Int:D @foo` would if i hadn't already assigned anything to it
kalkin- jmerelo: k, thank you 19:14
19:21 sena_kun joined 19:23 Altai-man_ left
kalkin- done 19:24
19:25 sauvin left 19:27 jmerelo left 19:32 mid_laptop joined
kalkin- .tell jmerelo the succ & pred stuff is magic. so I guess i need to do a PR which turns the MORE MAGIC switch on this ranges 19:35
tellable6 kalkin-, I'll pass your message to jmerelo
lizmat kalkin-: indeed :-) 19:38
kalkin-: you probably want to look at github.com/rakudo/rakudo/blob/mast...INC_DEC.p6 19:39
kalkin- lizmat: nice, thanks! now i know what to extend 19:40
m: say "๐Ÿ‚ค".succ; 19:41
camelia ๐Ÿ‚ค
kalkin- the question is how wild can i go? :)
cards? domino? majong? chess pieces? 19:42
they all have an internal order
19:45 Xliff_ left
lizmat anything with an internal order is ok to me... 19:50
as has been said: this is really magic :-)
kalkin- xahlee.info/comp/unicode_circled_numbers.html โ† Xah Lee has a good list of circled stuff
also do I need to add roast tests for that? 19:51
I would assume the behavior of Str.succ & Str.pred are part of the language definition 19:52
lizmat yes, I think there should be tests, I think there are, actually 19:53
19:53 mid_laptop left 19:54 mid_laptop joined
lizmat not too many, apparently :-( 19:55
Kaiepi oh it's the 23rd 20:13
.tell jmerelo, i'll get the post scheduled
tellable6 Kaiepi, I'll pass your message to jmerelo
20:17 AlexDani` joined
kalkin- Reading S26 I figured out that if you want to have trailing declarator block on a sub you have to define it like this: sub f() #= Trailing comment โค {} 20:18
20:18 AlexDaniel left
Kaiepi .tell jmerelo, oh mb didn't see the emails 20:18
tellable6 Kaiepi, I'll pass your message to jmerelo
kalkin- Ohh and leading/trailing pod on vars is broken. if there is a sub before the var, it declares the sub a multi and displays the variable pod as belonging to the sub. The var is lostโ€ฆ 20:21
chloekek Would be fun to write a COBOL parser with grammar. 20:28
tellable6 2019-12-23T19:01:36Z #raku <jmerelo> chloekek that's amazing. I'll check it out (I saw it on twitter, too)
lizmat chloekek: go for it :-) 20:29
chloekek It has some fun parsing rules regarding line continuations.
And of course the 7..72 columns limit. 20:30
20:39 pilne joined 20:40 rindolf left 20:46 stoned75 joined 20:59 pmurias joined 21:03 stoned75 left, vividsnow left, vividsnow joined 21:21 Altai-man_ joined, finanalyst joined 21:23 sena_kun left 21:33 vividsnow left 21:34 vividsnow joined 21:44 aluaces joined 21:47 aluaces left 21:52 mid_laptop left
xkr47 chloekek, use Inline::COBOL; # :-D 21:57
cpan-raku New module released to CPAN! CSS::Selector::To::XPath (0.0.6) by 03WARRINGD 22:24
22:40 gabiruh joined 22:43 guifa2 joined 22:52 dogbert11 joined 22:54 dogbert17 left 23:01 Kaiepi left 23:02 Kaiepi joined 23:07 wamba left 23:10 dogbert17 joined 23:12 dogbert11 left 23:21 sena_kun joined 23:23 Altai-man_ left 23:24 cpan-raku left 23:25 cpan-raku joined, cpan-raku left, cpan-raku joined 23:28 chloekek left
tbrowder kalkin: did you see reference to the "tree-sitter" streaming gramar parser mentioned i think by AlexDaniel a few weeks ago? 23:45
tellable6 2019-12-23T19:01:43Z #raku <jmerelo> tbrowder I'll check
2019-12-23T19:01:59Z #raku <jmerelo> tbrowder it's been published anyway, so we're good.
tbrowder *grammar
i was thinking that we might try to design a pod parser from scratch without regard (or minimum regard) to any previous grammar in the ambient code. then see if we can fit it back in either as a slang or just a rewrite of the current pod grammar. 23:50