🦋 Welcome to Raku! raku.org/ | evalbot usage: 'p6: say 3;' or /msg camelia p6: ... | irclog: colabti.org/irclogger/irclogger_log/raku
Set by ChanServ on 14 October 2019.
Geth doc: jjatria++ created pull request #3660:
Fix output for proto example		 08:56
Geth doc: 72cee90083 | (José Joaquín Atria)++ (committed by Juan Julián Merelo Guervós) | doc/Language/functions.pod6
Fix output for proto example

The listed output for the extended proto example did not match the code. The code example also had two separate functions with the same message, so that's been edited for clarity.		 09:37
linkable6 Link: docs.raku.org/language/functions
Geth doc: jjatria++ created pull request #3661:
Simplify use of pick in is-pure documentation		 10:24
Xliff \o 10:33
If I have a CArray from NativeCall... how can I know if .elems will return a proper size?
If I assign a CArray from a C-call, raku will complain that it doesn't know the length. 10:34
However if I create it from Raku, it will.
Is there a way to determine which is which?
timotimo `try $foo.elems` 10:35
Xliff timotimo: Hrm... 10:40
I take it if it's from C, that result would be a Failure object?
Geth doc: 07fa82e269 | (José Joaquín Atria)++ (committed using GitHub Web editor) | doc/Type/Routine.pod6
Simplify use of pick in is-pure documentation

Closes #3579		 10:44
doc: 8293b83357 | Altai-man++ (committed using GitHub Web editor) | doc/Type/Routine.pod6
Merge pull request #3661 from jjatria/patch-1

Simplify use of pick in is-pure documentation
linkable6 Link: docs.raku.org/type/Routine
linkable6 DOC#3579 [closed]: github.com/Raku/doc/issues/3579 [bug][docs] Fix "pick" use in docs.raku.org/routine/is%20pure
timotimo i would assume it throws an adhoc exception from moarvm 11:05
and that it doesn't translate that into a failure object in NativeCall itself
Xliff timotimo: OK, well I've written something that assumes that will become a Failure object at the Rakudo level. 11:11
timotimo: See usage, here: github.com/Xliff/p6-GLib/blob/mast...s.pm6#L137 11:12
JJAtria[m]1 jmerelo: I think we are talking about different things on that PR. I don't think there's actually any meaningful disagreement 11:35
tbrowder lizmat: when you get a chance please check my blog site to see if you can detect a raku post vs a non-raku one. 13:40
lizmat tbrowder: please remind us of the URL :-) 13:41
tbrowder please let me know how i can best arrange that: zola-blogs.us
tbrowder right now i have an html processing instruction that identifies the prog lang if any. but i can do all sorts of eye-ball invisible things 13:43
[Coke] tbrowder: light mode makes the code very hard to read, FYI
tbrowder i have two examples, are both bad? see latest 13:44
lizmat tbrowder: indented code block is only a black blob for me 13:44
tbrowder yes, i've filed issue with the Zola ppl 13:45
lizmat afk for 30 mins or so&
tbrowder it's the same for me
tbrowder [Coke] how about now. 13:47
both bad?
[Coke] I don't see a change. 13:47
first one still nearly invisible, second one is visible but low contrast (in light mode) 13:48
tbrowder ok, is contrast in dark mode ok?
tbrowder they have lots of highlighter schemes but i can't find examples. right now i'm trying to establish a minimally acceptable starting look, with tweaks to come with time. 13:50
[Coke] no, wasn't great, but was at least legible. 13:57
Don't want to get stuck in a QA cycle, just wanted to give you a quick heads up. :)
tbrowder ok, thnx, i just now found that many of zola's named highlight schemes can be seen. i'll put a link on my site so ppl can suggest something better. 14:17
lizmat And yet another Rakudo Weekly News hits the Net: rakudoweekly.blog/2020/10/05/2020-...anifestly/ 15:25
[Coke] gets name dropped in the weekly for doing the most basic of maintenance. :) 15:35
rypervenche I was quite surprised to see my name, forgot I submitted a PR. 15:39
[Coke] rypervenche++
tbrowder [Coke] i've updated site to show off code better with a slightly different highlighter. also added a link to the choices. suggestions welcome. 15:45
lizmat tbrowder: it's readable, but only barely :-( 15:46
tbrowder erg, all i can suggest is checking out some of the other choices. i'll consult codesections... 15:48
rypervenche Yeah, I kind of have to squint to be able to make out the different colors. And the bright background mixed with the all of a sudden very dark code block makes it harder to make out.
tbrowder rypervenche: note the little square at the top of the page allows you to switch from light to dark background 15:49
rypervenche Ahh, that's a bit better. I still think the difference in colors should be more pronounced though. 15:51
Perhaps a personal preference though.
tbrowder how do you like blog site of codesections ref colors and code highlighting? let me find link... 15:52
codesections.com 15:53
rypervenche I like that, but I'm probably biased there, as I use that colorscheme for my terminals :P 15:57
tbrowder codewise it doesn't look much different to me. i believe there is a way to choose the foreground and backgound colors and just forego syntax highlighting.
rypervenche To me the colors are more vibrant. 15:58
tbrowder i wouldn't have a prob with that but most would.
rypervenche Meh, you can't please everyone. Maybe come up with a few different options and get a vote from people? 16:00
tbrowder well my color perception is not that great, so it would really be helpful for someone to check out the other schemes on getzola.org 16:01
in the meantime, i'll see if i can isolate schemes to different code blocks 16:02
lizmat tbrowder: code gets better visually in dark mode indeed... but I prefer working in bright mode instead 16:04
rypervenche tbrowder: Where are the schemes on that site? 16:05
lizmat so switching to a dark mode blog is a bit of a pain, as you eyes need to adjust and/or you need to make sure no other bright windows blot out the dark mode blog
tbrowder rypervence: see the link referenced in my top sample blog at zola-blogs.us 16:09
rypervenche: ^^^
i like the default light background, but it may retain your last choice. 16:11
hm, i just took a look at codesections site. he uses "solarized-dark". if you all like his i can use his setup, including syntax higlighting... 16:16
rypervenche I went through them all. I like solarized and onehalf the best. But that's only my opinion. :) 16:22
Both of those colorschemes have light and dark versions. I don't know if it's possible to have those changed based on the light/dark theme that you choose. 16:26
tbrowder rypervenche: thnx, and i've changed my site to use solarized-dark but i'm not sure if i can see the difference. could you pls check and see if you can tell? 16:57
and i will definitely look into possibility of changing with choice of background! 16:58
rypervenche It looks the same to me.
lizmat it looks ever so slightly better to me (but then again, I know the power of suggestion)
perhaps because it is getting dark in my office as the sun is about to set 16:59
lizmat switches on a light
yeah, agree, no change
rypervenche The colors for "my" and "say" don't exist in solarized, and the other colors are not right either, so it doesn't look like it updated. 17:00
tbrowder ok, working on it. i will add codesections' raku extra syntax and that should help. will be later today before i can get to it. 17:05
bye-bye...
tbrowder alright, i *think* the solarized-dark highlight is actually being used (with Perl syntax coloring by Zola, not codesections' extra coloring). 19:35
can you eagle-eye color-sensitive ppl tell me if code block at zola-blogs.us looks different (hopefully a bit better)? 19:37
rypervenche tbrowder: Yep, it is correct now. 19:50
tbrowder so it looks better, great! thnx! now i'll see about adding the extra_syntaxes 19:51
klebs Hi everybody! anybody know how to expand the truncated IO::Path in this error message? 20:05
Constraint type check failed in binding to parameter '$target'; expected anonymous constraint to be met but got IO::Path (IO::Path.new("/tmp/m...)
klebs i am not sure why it truncates the text of the IO::Path 20:06
tbrowder .ask codesections is it ok to use yr raku.sublime-text syntax code? if so, what should attribution be? would it be ok to use in PR to Zola? 20:08
tellable6 tbrowder, I'll pass your message to codesections
klebs specifically, I want to know how to make raku automatically output the full path, when instead it outputs: "but got IO::Path (IO::Path.new("/tmp/m...)" 20:09
has anybody here encountered this? any fixes? I looked on the environment variables page, but didn't see anything that seemed to describe this issue 20:11
MasterDuke .tell klebs rakudo is deliberately shortening the string and i don't believe there's any user-facing way to prevent that. however, you can explicitly die in your constraint and give a different message. e.g., `sub a($a where {$_ == 1 or die "got $_"}){ say "hi" }(2)` 20:20
tellable6 MasterDuke, I'll pass your message to klebs
guifa m: sub foo($a, *@b) { }; say &foo.signature.params[1].positional 20:43
camelia False
guifa um....
guifa that doesn’t quite feel correct 20:45
lizmat m: sub foo(*@b) { }; say &foo.signature.params[0].positional 20:47
camelia False
lizmat m: sub foo(*@b) { }; dd &foo.signature.params[0]
camelia Parameter @b = *@b
MasterDuke m: sub foo($a, *@b) { }; say &foo.signature.params[1].slurpy
camelia True
lizmat feels like a buglet 20:48
guifa will make file an issue and see if he can track it down. 20:56
Just wanted to confirm it was not as designed. .named is false, but on *%slurpy, both .named and .slurpy are true (and .positional is false) 20:57
Geth ¦ problem-solving: lizmat unassigned from jnthn Issue META6 specification only exists "de facto" github.com/Raku/problem-solving/issues/236
¦ problem-solving: lizmat unassigned from jnthn Issue What is the philosophy of the Raku language github.com/Raku/problem-solving/issues/235 20:58
¦ problem-solving: lizmat unassigned from jnthn Issue IO::Path and Distribution::Resource share many methods github.com/Raku/problem-solving/issues/233
¦ problem-solving: lizmat unassigned from jnthn Issue Add a "community" label for issues that don't fit existing labels github.com/Raku/problem-solving/issues/232
¦ problem-solving: lizmat unassigned from jnthn Issue Ecosystem name resolution (or squatting) problem github.com/Raku/problem-solving/issues/229
¦ problem-solving: lizmat unassigned from jnthn Issue Coercion reconsidered and unified github.com/Raku/problem-solving/issues/227
¦ problem-solving: lizmat unassigned from jnthn Issue Extended identifiers-why and where, exactly? github.com/Raku/problem-solving/issues/224 20:59
¦ problem-solving: lizmat unassigned from jnthn Issue Map parameterized vs Hash parameterized github.com/Raku/problem-solving/issues/223
¦ problem-solving: lizmat unassigned from jnthn Issue Introspection for operator precedence, associativity github.com/Raku/problem-solving/issues/222
¦ problem-solving: lizmat unassigned from jnthn Issue .max on Iterables sorts on keys instead of values. github.com/Raku/problem-solving/issues/221 21:00
¦ problem-solving: lizmat unassigned from jnthn Issue Destructuring infinite ranges and sequences github.com/Raku/problem-solving/issues/218
¦ problem-solving: lizmat unassigned from jnthn Issue Loading of custom setting logic is undefined github.com/Raku/problem-solving/issues/213 21:01
¦ problem-solving: lizmat unassigned from jnthn Issue More language revision related questions needs resolving. github.com/Raku/problem-solving/issues/199
rypervenche guifa: There he is! Do you know of any module (or are any of the ones you're working on) that can handle date and time in almost any format? I was looking to find a single module that could go to and from RFC2822, but the two modules that look like they would handle that don't.
Geth ¦ problem-solving: lizmat unassigned from jnthn Issue Nativecall, native trait library usage rework github.com/Raku/problem-solving/issues/186 21:02
¦ problem-solving: lizmat unassigned from jnthn Issue A way to control Rat's behavior when it is running out of range for its denominator github.com/Raku/problem-solving/issues/185
rypervenche I made a PR for DateTime::Parse, but it doesn't look to be maintained anymore. I know that other language have a single library that can handle all/most date formats.
Geth ¦ problem-solving: lizmat unassigned from jnthn Issue What should be the size of `int`? (and other NativeCall type issues) github.com/Raku/problem-solving/issues/182
¦ problem-solving: lizmat unassigned from jnthn Issue A better MOP API for wrapper kinds could exist github.com/Raku/problem-solving/issues/180
lizmat hmmm... that's a lot of noise :-( 21:03
guifa rypervenche: sorry! was out of town and disconnected. Going to should be fairly simply enough via a formatter string, but the from is more difficult. 21:04
lemme check out the DateTime::Parse module and see if myabe I could do something with a PR there
rypervenche I only ask because right after I submitted the PR, I found an exception in an email date that appended (UTC) to the end of an RFC2822 date, which is not standard. I worked around it by fixing the string in my script, but it would be nice if we had a thing kind of like the Linux "date" command that can take all sorts of date formats as input. 21:05
rypervenche I was simply curious if we already had something like that that I wasn't aware of. 21:06
Geth ¦ problem-solving: lizmat unassigned from jnthn Issue Extended identifiers- reserving :sym puzzles me github.com/Raku/problem-solving/issues/225
guifa Actually, do you have a link to the Parse module? I can’t find it on the ecosystem
Geth ¦ problem-solving: lizmat unassigned from jnthn Issue Some useful math/statistics functions are missing github.com/Raku/problem-solving/issues/4 21:07
rypervenche github.com/sergot/datetime-parse/
guifa I’m not aware of one but it might not be bad to have a (potentially slower) but very accepting one. <local-time> will be fairly liberal, but won’t cover the ISO formats
rypervenche There is also github.com/raku-community-modules/...ime-format but it is missing the subroutine that I would need to parse a string into a DateTime object. 21:08
Geth ¦ problem-solving: lizmat unassigned from jnthn Issue Uncertain status of tests in the roast github.com/Raku/problem-solving/issues/217
¦ problem-solving: lizmat unassigned from jnthn Issue Use of literal named parameters syntax for multi-dispatching github.com/Raku/problem-solving/issues/195 21:09
¦ problem-solving: lizmat unassigned from jnthn Issue Inconsistent handling of too-large array index between match variables and regular arrays github.com/Raku/problem-solving/issues/10 21:10
¦ problem-solving: lizmat unassigned from jnthn Issue Raku and/or Rakudo trademarks github.com/Raku/problem-solving/issues/193
¦ problem-solving: lizmat unassigned from jnthn Issue Specify rounding mode in CORE github.com/Raku/problem-solving/issues/13
¦ problem-solving: lizmat unassigned from jnthn Issue take single letter CLI options with one leading hyphen, such as `-lwc` github.com/Raku/problem-solving/issues/18
Geth ¦ problem-solving: lizmat unassigned from jnthn Issue Metadata licenses should be required before adding new modules to ecosystem github.com/Raku/problem-solving/issues/19 21:10
¦ problem-solving: lizmat unassigned from jnthn Issue Use a grammar for command line options github.com/Raku/problem-solving/issues/187
¦ problem-solving: lizmat unassigned from jnthn Issue Semantics of coercion type on an "rw" parameter github.com/Raku/problem-solving/issues/21 21:11
Geth ¦ problem-solving: lizmat unassigned from jnthn Issue Defining custom coercions from extant types github.com/Raku/problem-solving/issues/22 21:11
¦ problem-solving: lizmat unassigned from jnthn Issue Removed Syntactic Feature (-i flag for in-place file editing) github.com/Raku/problem-solving/issues/36
¦ problem-solving: lizmat unassigned from jnthn Issue The ecosystem is a mess github.com/Raku/problem-solving/issues/39 21:12
¦ problem-solving: lizmat unassigned from jnthn Issue Please beware of eliminating (or changing) documented features github.com/Raku/problem-solving/issues/40
¦ problem-solving: lizmat unassigned from jnthn Issue `once` block can be executed more than once github.com/Raku/problem-solving/issues/41 21:17
¦ problem-solving: lizmat unassigned from jnthn Issue New named parameters to .classify github.com/Raku/problem-solving/issues/6
¦ problem-solving: lizmat unassigned from jnthn Issue where blocks vs sub signatures github.com/Raku/problem-solving/issues/24 21:18
¦ problem-solving: lizmat unassigned from jnthn Issue Editor modes for Raku github.com/Raku/problem-solving/issues/37
¦ problem-solving: lizmat unassigned from jnthn Issue Changelogging takes too much time and effort github.com/Raku/problem-solving/issues/53
guifa rypervenche: the DateTime::Format is an old module that was basically a port over of Perl stuff. I could probably take a look at it to see how to integrate it into other stuff I’m working on
Geth ¦ problem-solving: lizmat unassigned from jnthn Issue Release process changes github.com/Raku/problem-solving/issues/54 21:19
¦ problem-solving: lizmat unassigned from jnthn Issue Clarifying dual-licensing on the site github.com/Raku/problem-solving/issues/56
¦ problem-solving: lizmat unassigned from jnthn Issue Ecosystem issues and a corresponding dev github.com/Raku/problem-solving/issues/45
¦ problem-solving: lizmat self-assigned Clarifying dual-licensing on the site github.com/Raku/problem-solving/issues/56 21:20
¦ problem-solving: lizmat unassigned from jnthn Issue LCM (support Rat and fail on lossy coercion) github.com/Raku/problem-solving/issues/55
¦ problem-solving: lizmat unassigned from jnthn Issue X::MyModule::Foo or MyModule::X::Foo ? github.com/Raku/problem-solving/issues/57 21:21
¦ problem-solving: lizmat unassigned from jnthn Issue Ambiguity in pseudo-package and package reaction on missing symbols. github.com/Raku/problem-solving/issues/58
¦ problem-solving: lizmat unassigned from jnthn Issue Need a substitute for Perl 5 die with newline for raising end-user errors? github.com/Raku/problem-solving/issues/59 21:22
¦ problem-solving: lizmat unassigned from jnthn Issue Running some scripts without any input sometimes leads users to believe that the program is hanging github.com/Raku/problem-solving/issues/60 21:23
¦ problem-solving: lizmat unassigned from jnthn Issue What can and what cannot be changed in 6.c-errata? github.com/Raku/problem-solving/issues/62
¦ problem-solving: lizmat unassigned from jnthn Issue Should `without` allow chaining? github.com/Raku/problem-solving/issues/63 21:24
¦ problem-solving: lizmat unassigned from jnthn Issue Status of NativeCall is unclear github.com/Raku/problem-solving/issues/66
Geth ¦ problem-solving: lizmat unassigned from jnthn Issue Status of the POD6 implementation github.com/Raku/problem-solving/issues/69 21:26
¦ problem-solving: lizmat unassigned from jnthn Issue Official release of Raku implementation github.com/Raku/problem-solving/issues/70 21:27
¦ problem-solving: lizmat unassigned from jnthn Issue Should IO::Handle instances be possible to construct using file descriptors? github.com/Raku/problem-solving/issues/73 21:28
¦ problem-solving: lizmat self-assigned Should IO::Handle instances be possible to construct using file descriptors? github.com/Raku/problem-solving/issues/73
¦ problem-solving: lizmat unassigned from jnthn Issue Mechanism for Reusing Function Definitions in NativeCall github.com/Raku/problem-solving/issues/75
¦ problem-solving: lizmat unassigned from jnthn Issue Make Rakudo read from META6 modules with :ver<>, :auth<> and :api<> github.com/Raku/problem-solving/issues/76 21:29
¦ problem-solving: lizmat unassigned from jnthn Issue What's up with hyper/race semantics? github.com/Raku/problem-solving/issues/77
¦ problem-solving: lizmat unassigned from jnthn Issue Update Travis configuration so that it does not compile Rakudo every single time. github.com/Raku/problem-solving/issues/85 21:30
¦ problem-solving: lizmat unassigned from jnthn Issue Language versioning. github.com/Raku/problem-solving/issues/88 21:31
¦ problem-solving: lizmat unassigned from jnthn Issue Support for custom HOWs isn't generic enough github.com/Raku/problem-solving/issues/90
Geth ¦ problem-solving: lizmat unassigned from jnthn Issue .perl should be replaced with a pluggable system github.com/Raku/problem-solving/issues/91 21:33
¦ problem-solving: lizmat unassigned from jnthn Issue there is no security process for receiving security critical bug reports github.com/Raku/problem-solving/issues/92
¦ problem-solving: lizmat unassigned from rba Issue Alert system for core developers github.com/Raku/problem-solving/issues/95 21:34
¦ problem-solving: lizmat unassigned from jnthn Issue Alert system for core developers github.com/Raku/problem-solving/issues/95
¦ problem-solving: lizmat unassigned from jnthn Issue MoarVM Support of Callbacks in a Different Thread github.com/Raku/problem-solving/issues/96
Geth ¦ problem-solving: lizmat unassigned from jnthn Issue Clean interpolation for enumerated character classes github.com/Raku/problem-solving/issues/97 21:35
¦ problem-solving: lizmat unassigned from jnthn Issue Perl6 is missing the ability to store sub signatures for later use. Think Callbacks. github.com/Raku/problem-solving/issues/98 21:36
¦ problem-solving: lizmat unassigned from jnthn Issue stage0 is a binary blob, how can we do without it? github.com/Raku/problem-solving/issues/100
Geth ¦ problem-solving: lizmat unassigned from jnthn Issue Ecosystem stability issues github.com/Raku/problem-solving/issues/105 21:37
¦ problem-solving: lizmat unassigned from jnthn Issue Delegation does not handle multi-methods. github.com/Raku/problem-solving/issues/107
¦ problem-solving: lizmat unassigned from jnthn Issue Raku needs better ways to deal with network addresses github.com/Raku/problem-solving/issues/111
Geth ¦ problem-solving: lizmat unassigned from jnthn Issue Open a blog github.com/Raku/problem-solving/issues/115 21:39
El_Che poor jnthn will sleep wll tonight
Geth ¦ problem-solving: lizmat unassigned from jnthn Issue Creditcard for cloud services github.com/Raku/problem-solving/issues/117
Geth ¦ problem-solving: lizmat unassigned from jnthn Issue Wikipedia and Wikidata curation github.com/Raku/problem-solving/issues/120 21:43
¦ problem-solving: lizmat unassigned from jnthn Issue Check MoarVM out using OSS-fuzz github.com/Raku/problem-solving/issues/121
¦ problem-solving: lizmat unassigned from jnthn Issue List should have `.do` method as Supply github.com/Raku/problem-solving/issues/122
¦ problem-solving: lizmat unassigned from jnthn Issue `Supply.map` should respect the `Slip` semantics as `List.map` does github.com/Raku/problem-solving/issues/123 21:44
¦ problem-solving: lizmat unassigned from jnthn Issue Dynamic symbols resolution via &DYNAMIC is potentially a problem in user code github.com/Raku/problem-solving/issues/127 21:45
¦ problem-solving: lizmat unassigned from jnthn Issue "Path to Raku" is missing change of linux module namespaces github.com/Raku/problem-solving/issues/130
¦ problem-solving: lizmat unassigned from jnthn Issue Remove P5 regexes from Raku github.com/Raku/problem-solving/issues/133 21:47
¦ problem-solving: lizmat unassigned from jnthn Issue Add Dict/Tuple to the core github.com/Raku/problem-solving/issues/135 21:48
¦ problem-solving: lizmat unassigned from jnthn Issue perl6-users mailing list github.com/Raku/problem-solving/issues/139 21:49
¦ problem-solving: lizmat unassigned from jnthn Issue change the raku spec versioning github.com/Raku/problem-solving/issues/141
¦ problem-solving: lizmat unassigned from jnthn Issue Routines could use more support for reflection github.com/Raku/problem-solving/issues/149 21:50
¦ problem-solving: lizmat unassigned from jnthn Issue Expmod returns a default value instead of erroring out on libtommath errors github.com/Raku/problem-solving/issues/150
¦ problem-solving: lizmat unassigned from jnthn Issue RFE: returns for multiple variables github.com/Raku/problem-solving/issues/152 21:51
¦ problem-solving: lizmat unassigned from jnthn Issue uint's confused with int's github.com/Raku/problem-solving/issues/154 21:52
¦ problem-solving: lizmat unassigned from jnthn Issue IO::Socket::INET's methods for socket creation may need reconsideration github.com/Raku/problem-solving/issues/157
¦ problem-solving: lizmat unassigned from jnthn Issue The development experience around the generate-and-export pattern has shortcomings github.com/Raku/problem-solving/issues/159 21:53
¦ problem-solving: lizmat unassigned from jnthn Issue Errors indexing past the end of a List github.com/Raku/problem-solving/issues/160
¦ problem-solving: lizmat unassigned from jnthn Issue RAKUDOLIB destiny? github.com/Raku/problem-solving/issues/167
¦ problem-solving: lizmat unassigned from jnthn Issue Abandoned modules, deceased authors, etc. (Raku Community Modules) github.com/Raku/problem-solving/issues/168 21:54
¦ problem-solving: lizmat unassigned from jnthn Issue Making a signature accept a list of Pairs github.com/Raku/problem-solving/issues/177 21:55
lizmat That's it, all of problem solving tickets assigned to jnthn no longer assigned to him, sorry for the noise! 21:57
guifa lizmat I want to ++ but also kind of sad seeing it. Hopefully jnthn can rest and get well. 21:58
lizmat yes, similar feelings, I'm pretty sure jnthn will be able to rest and get well 21:59
we just have to make sure that #raku is a place he cannot do without :-) 22:00
guifa rypervenche: perhaps the best would be a DateTime::Format and DateTime::Parse that handle all of them. By default, the parser can check all formats with certain degree of leniency. The format one could just be a set of subs, since that’s what the :formatter option on DateTime takes 22:10
neither of those two modules are currently in the ecosystem, so I can be semi-evil and squat the name but making sure to keep it updated 22:11
rypervenche guifa: They're not? I found them from the modules.raku.org page. 22:35
guifa rypervenche: oh, hmmm, they weren’t use tags. I just clickeed on “date” tag ^_^ 22:41

Powered by Cro and the Raku® Programming Language.

Please report any issues / comments / feature requests as an issue on App::Raku::Log.

Thank you!