|
00:13
sivoais left
00:15
sivoais joined
02:01
m_athias left
02:02
m_athias joined
08:07
dakkar joined
|
|||
| Nemokosch | how do multis work when you hardcode the parameter value? What check happens on the actually passed value to determine if it matches? | 09:08 | |
| equivalence? smart-matching? | |||
| lizmat | the functional equivalent of smart-matching | 09:10 | |
| it tries to do short-cuts both at compile time as well as runtime | 09:11 | ||
| Nemokosch | so, to double-check: if I have a clause for f(1) and my call is f('1'), it can dispatch to the f(1) call? | 09:20 | |
|
09:22
discord-raku-bot left
09:23
discord-raku-bot joined
09:30
neither joined
10:30
neither left
10:50
neither joined
11:20
wingfold joined
12:56
razetime joined
13:51
neither left
14:42
jgaz joined
15:05
discord-raku-bot left,
discord-raku-bot joined
15:17
razetime left
15:27
razetime joined
15:52
jgaz left
16:41
dakkar left
16:51
jgaz joined
16:53
jgaz left
17:06
razetime left
17:58
n1to joined
18:03
discord-raku-bot left,
discord-raku-bot joined
|
|||
| Rogue | Well IntStr inherits from Int | 18:04 | |
| Nemokosch | okay but I wonder what kind of check is performer | 18:05 | |
| okay but I wonder what kind of check is performed | |||
| because <1> !~~ 1 | |||
| oops | |||
| I mean <1> \~\~ 1 indeed but '1' ~~ 1 too | |||
| and <1> !eqv 1 | |||
| Rogue | Yeah hm | ||
| I suspect it’s a two-step thing | 18:06 | ||
|
18:06
wingfold left
|
|||
| Type match and then maybe ACCEPTS | 18:07 | ||
|
18:12
discord-raku-bot left,
discord-raku-bot joined
19:00
MasterDuke left
19:21
MasterDuke joined
21:20
discord-raku-bot left,
discord-raku-bot joined
21:51
n1to left
|
|||