|
01:29
sibl joined
01:53
sibl left
02:21
arkiuat left
02:28
arkiuat joined
02:38
stanrifkin left
02:39
stanrifkin joined
03:53
stanrifkin_ joined
03:55
stanrifkin left
04:28
stanrifkin joined
04:30
stanrifkin_ left
05:13
arkiuat left
05:15
arkiuat joined
05:21
arkiuat left
05:34
arkiuat joined
05:41
arkiuat left
05:53
arkiuat joined
06:01
camelia joined
06:02
arkiuat left
06:15
arkiuat joined
06:19
arkiuat left
06:48
arkiuat joined
06:54
arkiuat left
06:56
arkiuat joined
07:00
arkiuat left
07:12
arkiuat joined
07:17
arkiuat left
07:30
arkiuat joined
07:56
arkiuat left
07:57
arkiuat joined
08:01
arkiuat left
08:13
arkiuat joined
08:22
arkiuat left
08:32
ACfromTX left
08:49
arkiuat joined
08:54
arkiuat left
09:09
arkiuat joined
09:13
arkiuat left
09:42
arkiuat joined
09:47
arkiuat left
10:15
arkiuat joined
10:19
arkiuat left
10:47
arkiuat joined
10:52
arkiuat left
11:17
arkiuat joined
11:24
arkiuat left
11:43
arkiuat joined
11:48
arkiuat left
12:01
arkiuat joined
12:06
arkiuat left
12:20
arkiuat joined
12:26
arkiuat left
13:00
arkiuat joined
14:38
ACfromTX joined
|
|||
| arkiuat | jubilatious1_98524, this is true, but the docs also use the word "module" in two different senses, and that's probably much more confusing than that the IO::Path method slurp has nothing to do with "slurpy" being a term for the behavior one kind of Signature parameter | 15:19 | |
| +Of | |||
| I guess it might be worthwhile to point that out though. Like two parentheticals, one in method slurp saying "No relation to L<slurpy parameters>" and then under the discussion of the latter "Nothing to do with <L IO::Path method slurp>" | 15:25 | ||
|
16:02
ds7832 joined
16:31
ds7832 left
|
|||
| jubilatious1_98524 | @arkuiat I should get on Github and make a suggestion then. Maybe something like my-slurp() will be clearer? That way, newbies won't waste time looking up the in-built slurp() routine/method. | 16:32 | |
| arkiuat | yeah, I don't think that's going to be any clearer at all. | 16:50 | |
| How does sticking a my- on front clarify anything? I don't get it. | 16:51 | ||
|
16:59
ds7832 joined
|
|||
| jubilatious1_98524 | @arkuiat Because no in-built Raku sub/method/routing will have my- prepended to it? Would you rather it read my-personally-modified-slurp() instead?? | 17:09 | |
|
17:58
arkiuat left
18:09
arkiuat joined
18:11
avuserow_ is now known as avuserow
18:15
arkiuat left
18:26
arkiuat joined
|
|||
| librasteve | I think we are stuck with the same term for reading from a file slurp and gathering all remaining arguments to a slurpy Array|Hash ... so my vote is to leave the code sub names alone and just have a short note that says do not confuse this with the file read routine called slurp | 18:28 | |
| jubilatious1_98524 | It's just three letters: sub my-slurp(*@pos) { say @pos; } | 19:18 | |
| ds7832 | that code example (the second under docs.raku.org/language/signatures#...ned_slurpy ) was introduced through a recent edit of mine. When I wrote it I must have been totally unaware of Raku.s own slurp() routine. The name should definitely be changed, IMO to something like "slurpy-routine" to leave no doubt that this has nothing to do with Raku's own slurp(). | 19:37 | |
| I'll add it to my active PR | 19:40 | ||
| Done: github.com/Raku/doc/pull/4678/comm...4b57f3b0c2 | 20:02 | ||
| thanks for the hints | 20:03 | ||
| By the way, this is the only place where the docs use the terms "Flattened slurpy" and "Unflattened slurpy". I think that more fitting would be the terms "Flattening slurpy" and "Non-flattening slurpy". This will then also match usage in docs.raku.org/type/List#Items,_fla...and_sigils such as "Slurpy parameters (*@a) flatten non-itemized sublists" | 20:25 | ||
| librasteve | ds: I agree | 20:41 | |
| ds7832 | Thanks, very good to have this confirmed. I'm writing on an commit to implement this | 20:43 | |
| librasteve | cool - its late for me now - so I will review tomorrow | 20:44 | |
|
20:45
librasteve_ joined
|
|||
| ds7832 | cool, have a good night! | 20:46 | |
| arkiuat | jubilatious1_98524, now I get. I hadn't realized you were talking about an example sub in a newly rewritten part of the docs. I thought you were talking about changing the name of the IO::Path method! | 20:57 | |
| +it | |||
|
22:16
arkiuat left
22:28
arkiuat joined
22:35
arkiuat left
22:52
ds7832 left,
arkiuat joined
22:57
arkiuat left
23:09
arkiuat joined
23:16
arkiuat left
23:21
arkiuat joined
|
|||