🦋 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.
shinobicl @tadzik , thanks, Cro::HTTP::Client worked perfectly :) 00:59
use v6;use Cro::HTTP::Client;use Data::StaticTable;my $resp = await Cro::HTTP::Client.get('api.pro.coinbase.com/products');my @body = await $resp.body;my $st = StaticTable.new(@body):set-of-hashes;print $st.display;
Xliff shinobicl: Why put the results of $resp.body in an @-var? 02:05
shinobicl because StaticTable's constructor can receive an array of hashes 03:13
github.com/shinobi/Data-StaticTabl...onstructor 03:16
rbt Is this not supposed to work? 03:45
my Str(Int) $var2 = 1;
The docs use that Str(Int) coercion (docs.perl6.org/syntax/Coercion%20type) but I get a compile error. 03:46
Int(Str) seems to work as expected.
Coercion Str(Int) is insufficiently type-like to qualify a variable
Juerd Neither Str(Int) nor Int(Str) works with 'my', here 04:34
They do both work in a sub signature
I fail to see the practical use of this feature with anything but Any, since the type it's coerced to itself isn't accepted. 04:37
"The method is assumed to return the correct type—no additional checks on the result are currently performed." 04:41
Interesting.
m: class Meh { method Str { return 42 } }; sub x(Str(Meh) $foo) { say $foo.WHAT, $foo }; x(Meh.new)
camelia (Int)42
Juerd I'd say that coercion types aren't type-like at all :) 04:43
shinobicl A small script to extract market data from Coinbase and get it as CSV files : pastebin.com/wa6D2N4S 08:03
Geth doc: 6d2c3c41e0 | (Stoned Elipot)++ | doc/Language/regexes.pod6
Keep example's code and output in sync
 09:34
Geth ¦ problem-solving: lizmat assigned to jnthn Issue How to provide coercers for new types in higher language versions github.com/perl6/problem-solving/issues/137 10:47
rbt Juerd: My trouble is actually a class "has" which I'm trying to pass a Json sourced variable into. Sometimes it's formatted like an Int and sometimes like a String. I can force cast of course, but I was hoping I could mark the class instead. 12:27
m: class a { has Str(Int) $.identifier = "not really an int";}; my Int $json-submitted-value = 1; my $n = a.new(identifier => $json-submitted-value);
camelia 5===SORRY!5=== Error while compiling <tmp>
Coercion Str(Int) is insufficiently type-like to qualify a variable
at <tmp>:1
------> 3class a { has Str(Int) $.identifier7⏏5 = "not really an int";}; my Int $json-s
expecting any of:…
El_Che still flappers on the new release 12:31
in misc
sena_kun tests new irc client 14:09
tbrowder .tell jmerelo post updated--basically done, but still some minor edits to make (i need to add another note), and i'll try to fix the wordpress issues with extra newlines. 14:35
tellable6 tbrowder, I'll pass your message to jmerelo
El_Che AlexDaniel`: I spoke to soon: the misc performance tests on i386 are frail 14:47
El_Che AlexDaniel`: I think yesterday evening travis had more free resources than today 15:10
AlexDaniel El_Che: is it the same goddamn test? 15:59
El_Che t/08-performance/99-misc.t ...................................... Dubious, test returned 1 (wstat 256, 0x100) 16:04
the same flapping bastard
dogbert17 Isn't that some kind of benchmarking test 16:29
El_Che it is 16:31
if it fails so badly on i386, image how it will fail in arm 16:32
if it fails 1 more time, I'll need to add an ifblock to disable testing on 32bit :( 16:44
El_Che and of course, it passed on the last run I wans planning to wait for :) 17:06
github.com/nxadm/rakudo-pkg/releas...g/v2019.11 <-- relocatabme builds on top 17:13
weekly: github.com/nxadm/rakudo-pkg/releas...g/v2019.11 <-- relocatabme builds on top
notable6 El_Che, Noted! (weekly)
El_Che Please: test the relocatable builds 17:23
Geth problem-solving/CoC: 594c2e0403 | (Elizabeth Mattijsen)++ | solutions/meta/CoC.md
Remove double negation:

So it becomes:
   We discriminate on the ability to be a kind, positive member of our community		 17:39
problem-solving/CoC: 37204bc9eb | (Elizabeth Mattijsen)++ | solutions/meta/CoC.md
Elaborate on standards of behavior
 17:43
Geth problem-solving/CoC: 099419cacd | (Elizabeth Mattijsen)++ | solutions/meta/CoC.md
Removed the "aside about trolls" paragraph

This indeed appears to be written in an era where trolls really were a major issue for Raku. After the change of name to Raku, this appears to be a lot less the case. So no reason to actually emphasize something that is quickly becoming a historical artefact.		 17:48
Geth problem-solving/CoC: dff95308b8 | (Elizabeth Mattijsen)++ | solutions/meta/CoC.md
Remove the quip about high level language

It feels very Perlish / TimToady-like. And hard to understand if you do not know the background of Raku and its long gestation process.		 17:52
Xliff What's the difference between ParametricRoleHOW and ParametricRoleGroupHOW? 17:54
lizmat a role vs grouping of roles of a class / role ? 17:56
Xliff Well, it's being used as a HOW for a single role so.... 17:57
Geth problem-solving/CoC: d7d4656206 | (Elizabeth Mattijsen)++ | solutions/meta/CoC.md
We **only** discriminate, japhb++
Xliff Aw...crap. 17:58
m: role A { }; A.HOW.^name.say
camelia Perl6::Metamodel::ParametricRoleGroupHOW
Xliff m: role A[::T] { }; A.HOW.^name.say
camelia Perl6::Metamodel::ParametricRoleGroupHOW
japhb lizmat: Comments on two of the CoC commits.
Xliff So now all roles are ParametricRoleGroups?
japhb *I added
japhb Ah, you saw one of them. :-) 17:59
Xliff m: role A[::T] { }; role B { also does A; }; A.HOW.^name.say; B.HOW.^name.say
camelia Perl6::Metamodel::ParametricRoleGroupHOW
Perl6::Metamodel::ParametricRoleGroupHOW
lizmat japhb: how about s/if you have a bad day/but will be bad for your karma/ ? 18:02
sena_kun AlexDaniel ping? 18:03
Geth problem-solving/CoC: 434311f73b | (Elizabeth Mattijsen)++ | solutions/meta/CoC.md
Mention effect on karma, rather than a possible reason

  japhb++ again.		 18:04
japhb lizmat++ # Yeah, I like that better. 18:06
Xliff m: role A[::T] { }; role B { }; A.HOW does B; A.HOW.^name.say 18:34
camelia Perl6::Metamodel::ParametricRoleGroupHOW+{B}
Xliff m: role A[::T] { }; role B { }; A.HOW does B; say A.HOW does Metamodel::ParametricRoleGroupHOW 18:36
camelia Cannot mix in non-composable type Perl6::Metamodel::ParametricRoleGroupHOW into object of type Perl6::Metamodel::ParametricRoleGroupHOW+{B}
in block <unit> at <tmp> line 1
Xliff m: role A[::T] { }; role B { }; A.HOW does B; say A.HOW ~~ Metamodel::ParametricRoleGroupHOW
camelia True
Xliff m: role A[::T] { }; role B { }; A.HOW does B; my @a := (Metamodel::ParametricRoleHOW, Metamodel::ParametricRoleGroupHOW); say A ~~ @a.any 18:37
camelia False
Xliff m: role A[::T] { }; role B { }; A.HOW does B; my @a := (Metamodel::ParametricRoleHOW, Metamodel::ParametricRoleGroupHOW); say A.HOW ~~ @a.any
camelia True
Geth problem-solving/CoC: f2b2694635 | (Elizabeth Mattijsen)++ | solutions/meta/CoC.md
Added section about good intentions and arbitration
 18:41
Xliff m: role A[::T] { }; role B { }; A.HOW does B; A.^roles.map( *.^name ).gist.say 18:51
camelia ()
Xliff OK, so how do I get an individual ParametricRoleHOW from a ParametricRoleGroupHOW? 18:53
tbrowder .seen jmerelo 19:02
tellable6 tbrowder, I saw jmerelo 2019-11-29T18:39:38Z in #raku-dev: <jmerelo> Point is, anyone wants to grab the remaining slot, just let me know, and in case Dec 9th is too early, let me know too.
tbrowder .tell jmerelo i took 9 dec slot. though i'm happy to give it up if someone else wants it, but speak soon! 19:03
tellable6 tbrowder, I'll pass your message to jmerelo
tbrowder .tell jmerelo check yr email 19:06
tellable6 tbrowder, I'll pass your message to jmerelo
Xliff OK. Method::Also is busted, again. :( 19:12
lucasb hey, Advent of Code starts soon (in 9 hours). Please join the private leaderboard I created last year, which already has some folks from the community. Code is 169430-b1c331b2 19:29
Geth doc: c0b771b54e | (JJ Merelo)++ | 2 files
Changes URL closes #3106
 19:59
MasterDuke i don't know how up-to-date the implementation is, might be a nice project for someone to update this github.com/kanaka/mal/tree/master/perl6 21:07
Geth problem-solving/CoC: f315ca777f | (Elizabeth Mattijsen)++ | solutions/meta/CoC.md
Define a troll as a person lacking of good intentions
problem-solving/CoC: 21c86e1f35 | (Elizabeth Mattijsen)++ | solutions/meta/CoC.md
First stab at a "Responsibility" section

Definitely *not* happy with the wording yet. Throwing it out there for feedback.		 21:16
Geth doc: 0ac1f113c1 | (Stoned Elipot)++ | doc/Language/grammar_tutorial.pod6
subject-verb agreement
 22:06
AlexDaniel sena_kun: pong 22:40
sena_kun AlexDaniel, o/ 22:48
AlexDaniel sena_kun: here's something interesting in the CoC github.com/perl6/problem-solving/p...0d50af6255 22:49
I have no idea why it is there and why it is so specific 22:50
jnthn Also, it's not really what's currently practiced; if a module in the ecosystem is broken the first resort is usually to see what might be done about it in Rakudo itself. 22:59
'cus it will often potentially break other code outside of the ecosystem too 23:00
AlexDaniel also even though I have been pushing for 0 breakage anywhere, it's not entirely achievable given that any bug fix can break someone's code 23:02
jnthn Indeed, there's some thinking and decision making involved. 23:02
I also wonder if this will put anyone off contributing. 23:03
Grinnz FWIW the general perl policy on that is, if it's because of a change in documented api compatibility must be maintained, if it's a change in internals people shouldn't be using the module should be fixed (with exceptions in extreme cases) 23:04
AlexDaniel Grinnz: I guess it means we're torturing ourselves a bit more :) 23:05
because even for stuff people shouldn't do/use we still do our best to not break existing code 23:06
Grinnz there's some of that in perl too, it's just a matter of where to draw the line
AlexDaniel we even have some back compat for actual bugs
.oO( the line seems to be right about at our necks )
 23:07
Grinnz :)
pm1.narvii.com/6948/cf3a2d94a18567f...v2_uhq.jpg 23:08
AlexDaniel anyway, point is that it is questionable CoC material.
tbrowder maybe so, 23:09
but it sounds like good policy 23:10
AlexDaniel I don't know. For example, I think there's room for a fast-moving compiler that doesn't care that much about backcompat 23:11
that section is very specific to rakudo so maybe that's a not a good point 23:12
but then maybe it should be part of contribution guidelines in rakudo, not part of CoC 23:13
lizmat fwiw, I'm too tired to digest all of the comments now, will look tomorrow 23:20
well, after some sleep& 23:21
sena_kun lizmat: have a good sleep!
AlexDaniel notable6: CLA github.com/rakudo/rakudo/files/3907677/CLA.pdf 23:50
notable6 AlexDaniel, Noted! (CLA)
AlexDaniel notable6: CLA
notable6 AlexDaniel, 2 notes: gist.github.com/34a4b159bc91840092...3a449d288d
AlexDaniel sena_kun: ↑ 23:51
sena_kun: is that ok?
AlexDaniel or should I make the font black? 23:52
it's currently gray
notable6: reset CLA 23:53
notable6 AlexDaniel, Moved existing notes to “CLA_2019-11-30T23:53:40Z”
AlexDaniel notable6: CLA www.perlfoundation.org/contributor...-agreement print it out, sign it, scan it in (resize your scan to 250KB or less). Email to trademark -at- perlfoundation.org and don't forget to CC will at coleda.com. PDF: github.com/rakudo/rakudo/files/3907678/CLA.pdf 23:54
notable6 AlexDaniel, Noted! (weekly)
AlexDaniel nooooo
AlexDaniel notable6: new-topic CLA 23:55
notable6 AlexDaniel, New topic added (“CLA”)
AlexDaniel notable6: CLA www.perlfoundation.org/contributor...-agreement print it out, sign it, scan it in (resize your scan to 250KB or less). Email to trademark -at- perlfoundation.org and don't forget to CC will at coleda.com. PDF: github.com/rakudo/rakudo/files/3907678/CLA.pdf
notable6 AlexDaniel, Noted! (CLA)
AlexDaniel ok the way it gists it is LTA but at least it works
[Coke]: I think there's a need to have a proper PDF 23:56
[Coke]: this one I made by printing to file from the website. I had to tweak a lot of css and html to get it to look right

Powered by Cro and the Raku® Programming Language.

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

Thank you!