|
🦋 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:05
donaldh left
08:10
[Tux] left
08:15
[Tux] joined
|
|||
| Geth | rakudo/DateTime-valuetype: 376b1dba7c | (Elizabeth Mattijsen)++ | src/core.c/DateTime.rakumod Make DateTime a value type I don't see a reason why it shouldn't be. Because the formatter is also part of the object, it uses the formatter's output as string in .WHICH. |
11:50 | |
| rakudo: lizmat++ created pull request #5933: Make DateTime a value type |
|||
| lizmat | do we actually have a description somewhere of what is expected / possible in a META6.json file ? | 12:25 | |
| jdv | ugexe or nine would know | 12:40 | |
| tellable6 | 2025-07-21T02:01:56Z #raku <tbrowder> jdv i just read what i replied and now i understand your confusion. what i was trying to say is that raku's class system encapsulates much of what Steven was showing us about closures in perl. and with much cleaner syntax. | ||
| jdv | tbrowder: ok | ||
| patrickb | I believe the best we have is in docs.raku.org/language/modules#Pre...the_module | 12:41 | |
| jdv | that looks like the old spec and the old spec is even linked! | 12:43 | |
| lizmat | hmm... I think we should remove the p6c section there, and move the fex section before the CPAN section | 12:45 | |
| patrickb | Right. the design docs are still the most encompassing text we have: github.com/Raku/old-design-docs/bl...format.pod | 12:46 | |
| lizmat | I guess github.com/Raku/old-design-docs/bl...ribution-1 | ||
| patrickb | lizmat: there is a PR by Weyland doing that. In the last phase of the review process: github.com/Raku/doc/pull/4570 | 12:47 | |
| lizmat | ah, good | ||
| patrickb | The old design docs are afaik still pretty accurate, but loads of the things stated there are not implemented. So there currently is no good reference of implemented stuff. | 12:50 | |
| jdv | in terms of regex perf and related - is anyone working on that? I think the 6.e checklist mentions it, right? | 12:51 | |
| lizmat | it does... but no guarantees there :-) | ||
| jdv | or was that more about rakuast perf regressions? | ||
| lizmat | don't think so | 12:52 | |
| jdv | who would know about that stuff, aside from timtoady? | ||
| or jnthn i guess. as they are both "out" at this point:( | |||
| lizmat | pmichaud jnthn | 12:53 | |
| yeah :-( | |||
| jdv | patrick is also "out" afaik | ||
| nine | S22 might be slightly dated (e.g. s/perl/raku/) but it's probably still the most authoritative source on this and AFAIK most of it is implemented as written. | 13:00 | |
| lizmat | thanks everyone, will take that as definition source for now while working on META6.json -> SBOM functionality | 13:01 | |
| ugexe | remember that arbitrary fields can be included as well | 14:14 | |
| as for why that is useful, here is an example from an old prototyping repository which stores file contents in the meta6.json file itself, and which can be installed to a CURI: github.com/ugexe/zef2/blob/5a9c581...#L107-L132 | 14:35 | ||
|
15:00
librasteve_ joined
15:17
nine left
15:18
nine joined
|
|||
| librasteve_ | teases rakudoweekly.blog/2025/07/21/2025-...-sleeping/ | 16:43 | |
| [Coke] cringes at the thought of there being youtube video of him out there again. :) | 16:50 | ||
| jdv | you be a celebrity now | 17:26 | |
|
17:50
guifa left
18:29
guifa joined
18:32
releasable6 left,
releasable6 joined
|
|||
| tbrowder | hi, i'm working on a new module that eases use of the GNU OpenType FreeFont and fiddling with what to name it. my current choice is 'GNU::FreeFont::OT'. any thoughts will be greatly appreciated. | 22:03 | |
| note OTF is the typical abbreviation but OT is a bit shorter and i believe is not unclear to font users | 22:04 | ||
| sorry. wrong channel | 22:51 | ||