|
This channel is intended for people just starting with the Raku Programming Language (raku.org). Logs are available at irclogs.raku.org/raku-beginner/live.html Set by lizmat on 8 June 2022. |
|||
|
01:43
kjp left
01:45
kjp joined
03:08
teatime joined
|
|||
| _elcaro_ | If you know you hex string is well formed (ie. $hex.chars %% 2) then you could just to $hex.comb(2) eg. my ($a, $b) = $hex.comb(2); | 04:00 | |
| bobby_jim_birdrock | That's the best of all. Thank you. | 06:33 | |
|
09:23
r1111l joined,
r1111l left
|
|||
| timemelon | can somebody point to the docs that talk about referring to operators as terms? eg &infix:<+> and &[+] | 09:46 | |
| lizmat | strictly speaking, &infix:<+> is the subroutine name for the infix + operator | 09:53 | |
| and &[+] is a grammar construct to refer to &infix:<+> in a shorthand way | |||
| dr.shuppet | I'm far from an expert on this, but from what I know, operators are just subs with a non-standard name: > &infix:<+>.WHAT (Sub+{is-pure}) Also see docs.raku.org/language/optut. The way to refer them as terms is a form of extended identifier: docs.raku.org/language/syntax#Exte...dentifiers | 09:54 | |
| The extended identifier works just like any other sub identifier: > infix:<+>(5, 6) 11 | 09:58 | ||
| timemelon | thank you both! | 10:00 | |
| lizmat | m: dd &[+] =:= &infix:<+> # they're really the same | 10:21 | |
| camelia | Bool::True | ||
| dr.shuppet | Yeah I think &[+] is just syntactic sugar (correct me if I’m wrong) | 10:28 | |
| lizmat | yup, it is | ||
| dr.shuppet | The actual symbol being &infix:<+> | ||
| I found it in roast also: github.com/Raku/roast/blob/master/...name.t#L71 | 11:39 | ||
| And if you still doubt it is really syntactic sugar: [0] > \&[RandomNonsense] ===SORRY!=== Missing infix inside R ------> \&[R⏏andomNonsense] expecting any of: infix infix noun infix stopper statement list term Other potential difficulties: To pass an array, hash or sub to a function in Raku, just pass it as is. For other uses of Perl's ref operator | 11:43 | ||
| consider binding with ::= instead. Parenthesize as \(...) if you intended a capture of a single variable. ------> \⏏&[RandomNonsense] [0] > &[randomNonsense] ===SORRY!=== Error while compiling: Missing infix inside [] ------> &[⏏randomNonsense] expecting any of: infix infix noun infix stopper statement list term | |||
| Unlike this: [0] > &infix:<test> ===SORRY!=== Error while compiling: Undeclared routine: infix:<test> used at line 1. Did you mean 'infix:<+^>', 'infix:<⚛=>', 'infix:<÷>', 'infix:<∈>', 'infix:<⩶>'? which is just parsed as an identifier, looked up in symbol table, and failing | 11:44 | ||
| lizmat | and yet another Rakudo Weekly News hits the Net: rakudoweekly.blog/2024/04/08/2024-14-15-1k-75/ | 12:45 | |
| dr.shuppet | Nice, I haven't been watching the developments about Raku for a while, glad to see things are moving forward! | 12:56 | |
| antononcube | Sideways, too! | 13:11 | |
| Hmm... to clarify, I see the LLM endowments as "sideway" developments. I still think Raku-LLM is the best combination for most LLM related workflows, but at some point the language ecosystems start to become a factor. | 13:15 | ||
| bobby_jim_birdrock | m: my $hex = '0810'; my ($col, $row) = $hex.comb(2); | 14:22 | |
| Raku eval | |||
|
14:41
vlad joined
14:42
vlad left
14:46
vlad joined
15:47
gfldex left
16:38
teatwo joined
16:42
teatime left,
discord-raku-bot left
16:43
discord-raku-bot joined
16:44
gfldex joined
16:53
teatwo left,
teatwo joined
17:12
MasterDuke left
20:01
vlad left
21:25
cleo joined
22:06
hudo left
22:08
hudo joined
23:40
deadmarshal_ left
23:46
deadmarshal_ joined
|
|||