|
🦋 Welcome to the IRC channel of the core developers of the Raku Programming Language (raku.org #rakulang). This channel is logged for the purpose of history keeping about its development | evalbot usage: 'm: say 3;' or /msg camelia m: ... | log inspection situation still under development | For MoarVM see #moarvm Set by lizmat on 22 May 2021. |
|||
|
00:02
reportable6 left
00:05
reportable6 joined
00:52
[Coke] left,
[Coke] joined
03:35
reportable6 left,
coverable6 left,
statisfiable6 left,
quotable6 left,
linkable6 left,
shareable6_ left,
bisectable6 left,
tellable6 left,
committable6_ left,
benchable6 left,
notable6_ left,
bloatable6 left,
squashable6 left,
evalable6 left,
greppable6 left,
sourceable6 left,
releasable6 left,
nativecallable6 left,
unicodable6 left,
shareable6 joined
03:36
benchable6 joined
03:37
tellable6 joined,
bloatable6 joined,
quotable6 joined,
evalable6 joined,
greppable6 joined,
sourceable6 joined,
unicodable6 joined,
nativecallable6 joined,
reportable6 joined
04:36
notable6 joined
04:37
bisectable6 joined,
squashable6 joined
04:38
linkable6 joined
05:36
committable6 joined
05:37
statisfiable6 joined
05:38
releasable6 joined
06:02
reportable6 left
06:36
coverable6 joined
06:38
CIAvash joined
|
|||
| moon-child | should bug fixes generally also turn into spectests? My intuition is yes, but it doesn't seem to happen generally, even given r3 (which makes testcases for bug reports, but those don't go into roast) | 07:00 | |
|
08:03
reportable6 joined
12:02
reportable6 left
12:08
sena_kun left
12:41
sena_kun joined
|
|||
| ugexe | generally yeah, but of course it depends | 13:50 | |
|
14:01
linkable6 left,
evalable6 left,
linkable6 joined
15:01
linkable6 left,
committable6 left
15:02
evalable6 joined
15:04
reportable6 joined
15:56
costledger_ joined
15:58
costledger_ left
|
|||
| japhb | moon-child: If they are tests of *generally agreed Raku* functionality, yes. If they are tests of *Rakudo-specific* functionality, they should be tested in Rakudo's individual test suite. Then there are things that we can tell are broken currently (and so should be "fixed" with something less broken), but not sure exactly how to describe the behavior we want without limiting our options for "correct" | 16:00 | |
| behavior in the future. | |||
|
16:02
linkable6 joined
16:26
casaca left
16:30
casaca joined
18:02
reportable6 left
19:03
reportable6 joined
19:04
committable6 joined
|
|||
| vrurg | nine: github.com/rakudo/rakudo/pull/4538 | 19:52 | |
| Geth | problem-solving/JJ-patch-1: 9039f9e69a | (Juan Julián Merelo Guervós)++ (committed using GitHub Web editor) | solutions/meta/TheRakuFoundation.md Communicating the effective establishment The Raku Foundation exists, so this closes #263 |
19:54 | |
| problem-solving: JJ++ created pull request #300: Communicating the effective establishment of the Raku foundation |
19:55 | ||
|
23:29
evalable6 left,
linkable6 left
23:31
linkable6 joined
|
|||