00:04 librasteve_ left
Geth doc/main: 1ff280b863 | 2colours++ | 2 files
Add and reference new `."" operator` entry
04:25
doc/main: f9eef345cd | (Eric Forste)++ (committed using GitHub Web editor) | 2 files
Merge pull request #4769 from 2colours/runtime-method-names

Add and reference new `."" operator` entry
lizmat docs.raku.org/routine/is%20rw doesn't mention containers, I think it should as there is a whole page explaining containers in Raku: docs.raku.org/language/containers 12:15
also I think the example there is too complicated: something like: 12:16
my $a; sub foo() is rw { $a }; foo() = 42; say $a
should really be enough to get the point across
also, the statement "When a routine is modified with this trait, its return value will be writable." is incorrect 12:33
m: sub a() is rw { 42 }; a() = 666
camelia Cannot modify an immutable Int (42)
in block <unit> at <tmp> line 1
12:34
lizmat so I think the language should be more container centric, and mention that "is rw" will not de-containerize
another (maybe known issue): docs.raku.org/syntax/DWIM shows a link to WAT 13:19
however, the link as a link to an anchor on the same page, rather than to: docs.raku.org/syntax/WAT (and vice-versa) 13:20
so theses generated pages would need to have their links inlocalized? 13:21
[Coke] That bug sounds familiar. 13:35
but I don't see it on doc-website, where I'd expect it. 13:40
lizmat: github.com/Raku/doc-website/issues/483 13:49
14:07 samebchase2 joined
nemokosch returning a non-writable value from an is rw sub seems like a DIHWIDT at best 14:07
14:09 samebchase left, samebchase2 is now known as samebchase
sub modify($a is rw) { $a = 42; }; modify(53); # this throws without ever executing the body 14:09
as things are, is there even a difference between is rw and is raw for return values? 14:11
the current code example is a bit scary for sure 14:16
16:59 finanalyst_ joined