gfldex | m: "..##".trans: . => a, # => e; # Rakudo, how clever are you? | 00:11 | |
m: m: "..##".trans: '.' => a, '#' => e; # Rakudo, how clever are you? | |||
m: m: "..##".trans: '.' => 'a', '#' => 'e'; # Rakudo, how clever are you? | 00:13 | ||
m: "..##".trans: '.' => 'a', '#' => 'e'; # Rakudo, how clever are you? | |||
m: say "..##".trans: '.' => 'a', '#' => 'e'; | |||
m: say "..##".trans: <. #> => <a e>; | 00:15 | ||
This should have been covered by github.com/rakudo/rakudo/issues/2118 | 00:21 | ||
This is a nice example, that test driven programming works well -- with the right kinds of tests. | 00:33 | ||
Hydrazer | oeuf | 01:39 | |
gfldex | m:``` | 03:30 | |
multi sub possible($a, $b where { $a == $b² }) { say „$a is $b²“ } | |||
multi sub possible($a, $b where { $a =~= $b²}) { say „$a is possibly $b²“ } | |||
multi sub possible(| ($a, $b)) { say „$a is not $b²“ } | |||
possible 1, -1; | |||
possible 2, sqrt(2); | |||
possible 4, 4; | |||
``` | |||
Nemokosch | So can you confirm that this still isn't the right behavior for # inside tr? | 06:44 | |
07:47
parv left
|
|||
gfldex | So far there was no reply in <#633753335119478795> . | 08:31 | |
09:01
dakkar joined
11:30
TempIRCLogger left
11:31
TempIRCLogger joined
11:38
TempIRCLogger left,
TempIRCLogger joined
11:44
TempIRCLogger left,
TempIRCLogger joined,
TempIRCLogger left,
TempIRCLogger joined,
TempIRCLogger left,
TempIRCLogger joined
11:45
TempIRCLogger left,
TempIRCLogger joined,
TempIRCLogger left,
TempIRCLogger joined,
TempIRCLogger left,
TempIRCLogger joined,
TempIRCLogger left,
TempIRCLogger joined,
TempIRCLogger left
12:07
TempIRCLogger joined
12:12
TempIRCLogger left,
TempIRCLogger joined
12:16
TempIRCLogger left,
TempIRCLogger joined
|
|||
Nemokosch | 😬 | 12:18 | |
12:22
TempIRCLogger left,
TempIRCLogger joined
13:00
TempIRCLogger left,
TempIRCLogger joined,
TempIRCLogger left,
TempIRCLogger joined
13:25
TempIRCLogger left,
TempIRCLogger joined,
TempIRCLogger left
13:26
TempIRCLogger joined
13:27
TempIRCLogger left,
TempIRCLogger joined,
TempIRCLogger left
13:28
TempIRCLogger joined
13:37
TempIRCLogger left,
TempIRCLogger joined
13:44
TempIRCLogger left
13:45
TempIRCLogger joined
13:52
TempIRCLogger left,
TempIRCLogger joined
13:58
TempIRCLogger left,
TempIRCLogger joined
14:11
TempIRCLogger left,
TempIRCLogger joined
14:12
TempIRCLogger left,
TempIRCLogger joined
14:59
halcek joined
|
|||
halcek | Uploaded file: uploads.kiwiirc.com/files/56f004e6...pasted.txt | 14:59 | |
Hi, a quick question: Is, or could there be there some built-in function in Raku, equivalent to Ruby's times? So that you can set repeating a value by using a keyword (such as times, in 5.times ( print "T" ) , or something like print "T" 5.times, which is grammatically natural for a novice, instead of an operator being the only possibility to | 15:00 | ||
induce this like: print "T" x 5? | |||
lizmat | m: print "T" for ^5 | ||
camelia | TTTTT | ||
lizmat | halcek ^^ | 15:01 | |
halcek | lizmat yes, something like that! Thanks, | ||
15:01
halcek left
|
|||
SmokeMachine | m: print(“T”) xx 5 | 15:31 | |
camelia | TTTTT | ||
lizmat | m: say print(“T”) xx 5 | 15:33 | |
camelia | TTTTT(True True True True True) | ||
lizmat | I generally consider xx to not be used for its side-effects, but you're right, you could do it like that as well :-) | ||
Nemokosch | what side effects? | 15:39 | |
SmokeMachine | The printed string | 15:40 | |
Nemokosch | oh I misunderstood it for 'T' xx 5 | 15:41 | |
17:37
dakkar left
19:49
TempIRCLogger left
19:50
TempIRCLogger joined
|