I implemented the first non-trivial Str.Numeric. When true allomorphs became a thing, the bulk of that code was moved into val(Str:D). I claim no responsibility for the non-number-parsing bits of val().

.tell Zoffix re: IRC::Client::Plugin::Factoid and maybe IRC::Client : Curious if you were aware that bots aren't supposed to reply to NOTICE's, and if so how come you chose to do otherwise. Also curious if the Factoid plugin is still something you're actively using/developing; I'm planning some changes, willing to coordinate design changes and pushing them upstream if you'd like.

03:46Z <teatime> Zoffix: re: IRC::Client::Plugin::Factoid and maybe IRC::Client : Curious if you were aware that bots aren't supposed to reply to NOTICE's, and if so how come you chose to do otherwise. Also curious if the Factoid plugin is still something you're actively using/developing; I'm planning some changes, willing to coordinate design changes and pushing them upstream if you'd like.

teatime, because replies to NOTICE are useful to me and I couldn't care less what the RFC no one is following strictly says. I'm not developing Factoid at the time, though IIRC it does have a DESIGN document that describes functionality it was planned to have

Spotted this in my grocery store last night and, seeing it's made in Toronto, I'm convinced there's a bunch of people betting each other on which outrageous company name they can get away with: http://i.imgur.com/qcu4G6V.jpg

cono: you can tell the variable what ita default value is. Since Nil means no value, if you assign it to the variable, you get its default value. The default default is a type object of the same type as explicit type constraint on the variable, unless there isn't one, in which case it's Any

cono: so all the stuff I explained about Nil being more appropriate than Any to return and that being new behaviour..... it's implemented using too broad a stroke and assumes that any type object being made means no match

marcusramberg: git clone gitgithub.com:croservices/cro-core as well as cro-ssl and patch lib/Cro/SSL.pm6 and lib/Cro/TCP.pm6 respectively to return some random value from the four methods {peer,socket}-{host,port}

Yeah, Cro depends on 2017.08 at least. In part for the feature mentioned, but far more so because working on it uncovered a nasty memory leak that was also fixed in 2017.08, and you'd really not want to run it with that leak.

I think Along with The White Book, The Gray Book, and The Black Book, there's bee The Green Book, which is half-a-book sided intro to absolute programming beginners who'd read it before going to The White Book

Aaronepower: basically, you're trying to parse the number and then looking for the postfix modifier (min/hr) if you fail to find it you need to backtrack to match the number again for the other token. And I'm guessing the failure to match I'm seeing is because after failing to match one token, it goes for <digit> again and fails to match that. Just rewrite your grammar to not require backtracking. As one Tim

To me, it makes sense that <ws> would match whitespace, and not a lack thereof. A modifier can be used to match something or nothing, but because a modifier cannot turn a token that's \s* into \s+, it makes sense to have the token be \s+ and allow a ? to effectively turn it into \s*