|
🦋 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: ... | Logs available at irclogs.raku.org/raku-dev/live.html | For MoarVM see #moarvm Set by lizmat on 8 June 2022. |
|||
|
08:26
guifa_ joined
08:27
guifa left,
camelia left,
kjp left
08:28
kjp joined
08:46
camelia joined
09:00
camelia left
09:19
camelia joined
|
|||
| nine | Why not just have that file declare the language version that it was written against? | 09:41 | |
| I.e. a simple use v6.d; at the top | 09:43 | ||
| lizmat | I've considered that, but felt that was less future proof? | 09:45 | |
| nine | But that's the whole point of declaring that language version? | 09:46 | |
| lizmat | when we release 6.e, then the "use v6.e.PREVIEW" can be removed from the file | ||
| nine | Which will then again make it less future proof. Adding a use v6.d; once will fix it forever | 09:47 | |
| lizmat | otherwise the "use v6.d" will remain there for eternity, and will cause problems once 6.d is no longer supported ? | ||
| nine | Why would 6.d ever not be supported? | ||
| lizmat | because it might ? | ||
| and we would be no longer around to tell why we put a "use v6.d" in there ? | 09:48 | ||
| nine | We don't have to. The use v6.d should always have been there. I simply forgot to add it. | 09:49 | |
| The whole reason for adding such a language version tag is to be safe against random future changes of the language. By definition you can't predict what those are going to be. | 09:50 | ||
| Geth | rakudo/main: e591b023d1 | (Elizabeth Mattijsen)++ | lib/NativeCall/Dispatcher.rakumod Freeze NativeCall::Dispatchers to 6.d |
09:51 | |
| roast: 91481b1212 | (Elizabeth Mattijsen)++ | 7 files Move 6.d specific tests to the right place and activate them The behaviour of log() / sign() / sqrt() changes from 6.d to 6.e, so they need to be tested as part of 6.d specific tests, *not* as part of 6.c specific tests. So move them to the "6.d" directory, force "use v6.d" on them and add those to the spectest.data file |
09:54 | ||
| lizmat | RAKU_LANGUAGE_VERSION=6.* RAKUDO_RAKUAST=1 raku -e 'use v6.c; "42".EVAL' | 10:22 | |
| No compiler available for Raku 6.* | |||
| meh | |||
| will look at that later today / tomorrow | |||