IRCloggy #perl6-dev 2019-09-09

Logs Search ←Prev date Next date→ Channels Documentation

Provider of IRC logs since 2005.
WARNING: As Freenode became unjoinable and lost all warnings in topics, we cannot log channels on Freenode anymore.

2019-09-09

lucasb left00:04
Kaiepi left00:05
Xliff left00:41
Geth ¦ roast: vrurg++ created pull request #575: Add tests for decontainerization of Hash -> Map coercion 00:45
¦ roast: review: https://github.com/perl6/roast/pull/57500:45
¦ rakudo: vrurg++ created pull request #3174: Provide means of preserving the decontainerization of values on Hash -> Map coercion 00:56
¦ rakudo: review: https://github.com/rakudo/rakudo/pull/317400:56
¦ rakudo: vrurg self-assigned Unpacking a |%h.Map has a different behaviour from 2019.07.1 https://github.com/rakudo/rakudo/issues/316801:01
Kaiepi joined02:02
Geth ¦ rakudo: vrurg++ created pull request #3175: Further cleanup of build subsystem. 02:39
¦ rakudo: review: https://github.com/rakudo/rakudo/pull/317502:39
¦ rakudo/master: 7 commits pushed by (Vadim Belman)++02:41
¦ rakudo/master: 499b15b4fd | nqp-configure submodule update 02:41
¦ rakudo/master: 7cf2481d34 | Merge branch 'master' of https://github.com/rakudo/rakudo into rakudo_3151 02:41
¦ rakudo/master: ab7e5559e5 | Add rakudo.js and perl6-debug.js to .gitignore 02:41
¦ rakudo/master: a69fdc41e6 | Futher unification of JS backend with others 02:41
¦ rakudo/master: 6c1af04e14 | Fix <backend>_HARNESS_TYPE not been set 02:41
¦ rakudo/master: b0fc0fa158 | Make COREs compile in blib 02:41
¦ rakudo/master: 59e683f680 | Merge pull request #3175 from vrurg/rakudo_3151 02:41
¦ rakudo/master: review: https://github.com/rakudo/rakudo/compare/66e0561f91c6...59e683f6807502:41
vrurg .tell pmurias Please, check my latest merge. I made it compile perl6.js and copy it into rakudo.js for back compat purpose. Otherwise things work on my macos and even passes most core tests.02:42
tellable6 vrurg, I'll pass your message to pmurias02:42
evalable6 left03:04
Kaiepi left03:05
evalable6 joined03:05
[Tux] Rakudo version 2019.07.1-260-g9dd67cb37 - MoarVM version 2019.07.1-188-g289e9dfce04:30
csv-test-xs-20 0.440 - 0.44004:30
csv-ip5xs 0.740 - 0.74604:30
test-t --race 0.892 - 0.92004:30
test-t 1.810 - 1.87504:30
csv-ip5xs-20 5.100 - 5.42404:30
test 6.943 - 7.27804:30
test-t-20 --race 9.471 - 9.67304:30
csv-parser 21.994 - 23.82004:30
test-t-20 30.187 - 31.12404:30
(from yesterday)04:30
Kaiepi joined05:01
robertle left05:48
Kaiepi left06:04
Geth ¦ problem-solving: AlexDaniel assigned to jnthn Issue stage0 is a binary blob, how can we do without it? https://github.com/perl6/problem-solving/issues/10006:54
robertle joined07:50
Kaiepi joined08:16
Kaiepi left08:45
leont joined08:51
leont left08:57
Kaiepi joined10:57
lizmat joined11:53
lizmat .12:02
tellable6 2019-08-26T21:53:56Z #moarvm <japhb> lizmat: I have not been using forcegc; frankly I'd just like to detect that a GC *happened*, and get an idea of which parts of a complicated test run are causing GC churn and which ones are relatively "GC quiet"12:02
2019-09-05T01:28:32Z #perl6-dev <AlexDaniel> lizmat: .unival is now *much* faster than just 2x https://colabti.org/irclogger/irclogger_log/perl6-dev?date=2019-09-05#l712:02
2019-09-05T15:29:59Z #perl6 <Grinnz> lizmat: maybe you should edit your early post that suggests camelia to indicate the direction changed to raku, since new commenters (understandably) aren't reading all of the posts to find this out12:02
2019-09-08T15:28:40Z #whateverable <Xliff> lizmat Do you still have plushie camelias available?12:02
https://gist.github.com/80cd35795ecc19710e53c992c8c1c31d12:02
lizmat left12:45
lizmat joined12:50
camelCaser left13:28
lucasb joined13:42
japhb OK, it's a little weird that it would gist a single remaining line. Is it because of that line's length?13:56
Also, if it's going to decide to gist at all, why not gist all of them sent to the same user?13:57
(in one gist, I mean)13:57
timotimo tellable6: source14:05
tellable6 timotimo, https://github.com/perl6/whateverable14:05
timotimo :P14:05
vrurg japhb: the last line just happens to be too long to fit into IRC standard.14:10
lizmat how did it get into it then ?14:13
I mean, from an IRC message, I presume ?14:13
timotimo tellable puts a bunch of stuff in front of the message itself14:13
AlexDaniel actually it's probably not too long, but almost too long. Tellable is probably overcautious14:37
but yeah, it should be fixed14:38
timotimo the whateverables could talk to each other to figure out the maximum message length14:38
AlexDaniel jnthn: I don't quite get your answer… So you think that what we have is OK for debian, and we're going to ignore that issue until they tell us otherwise?14:45
jnthn AlexDaniel: I don't know what we can realistically do about the issue even if they did tell us otherwise.14:59
But such a policy would essentially mean "you can't use a bootstrapped compiler unless you're so successful you have multiple competing implementations" or something.15:00
AlexDaniel jnthn: what about creating a micro implementation of nqp that's full enough for bootstrapping purposes?15:02
it doesn't sound fun or quick, but still15:04
jnthn a) it wouldn't be very micro given it needs to compile a large part of grammers, support OO, etc. b) "what about" - *who* is going to do that?15:04
The answer is "probably nobody".15:05
Unless somebody shows up who is specifically interested to do that :)15:05
AlexDaniel like a gsoc project, or something? ;)15:06
jnthn There's so many better things I can think of to do with a gsoc project :/15:06
AlexDaniel ok I got it, thanks15:06
jnthn Basically, I find the issue a bit academic/unpragmatic.15:07
AlexDaniel .tell robertle please let me know if what we have with stage0 is ok for debian or not. I created this ticket https://github.com/perl6/problem-solving/issues/10015:09
tellable6 AlexDaniel, I'll pass your message to robertle15:09
AlexDaniel .tell robertle Basically, the upstream guide talks about compiling for other architectures, but we don't have this problem. The only problem is purity of the build itself (“Reflections on Trusting Trust” stuff)15:09
tellable6 AlexDaniel, I'll pass your message to robertle15:09
AlexDaniel if it's not ok for debian and they throw our package away, then the issue is very pragmatic15:11
so that's why asked my first question the way I did, so it's ok and we just wait15:12
robertle left15:39
Kaiepi left16:07
MasterDuke left16:19
Kaiepi joined16:37
robertle joined16:51
grayrider left17:07
camelCaser joined17:19
camelCaser left17:28
camelCaser joined17:28
MasterDuke joined18:28
sortiz joined19:39
sortiz left19:44
Ven`` joined20:38
Xliff joined20:42
Xliff SmokeMachine: https://paste.fedoraproject.org/paste/XL0L6I5tOQTg8kDkxzb9BQ20:43
tellable6 2019-09-09T19:03:00Z #perl6 <patrickb> Xliff re DBIish and MSSQL using DBDish::ODBC. I use that in a production system at work20:43
2019-09-09T19:04:21Z #perl6 <patrickb> Xliff Prepared statements do not work and are not trivial to implement.20:43
2019-09-09T19:07:39Z #perl6 <patrickb> Xliff there is also a PR waiting for merge that fixes some column types https://github.com/salortiz/DBDish-ODBC/pull/520:43
Xliff .tell patrickb Thanks for the information. I was hoping it would be as simple as mapping to the right routine.20:44
tellable6 Xliff, I'll pass your message to patrickb20:44
SmokeMachine Xliff: What's the code you are using to test?20:44
Xliff Coming up.20:44
https://paste.fedoraproject.org/paste/chSTlQ4tqhhIe8Y7vObucg20:45
SmokeMachine Xliff: does it work if you run: `say $*RED-DB.execute: "select * from poe"`?20:54
lizmat notable6: weekly21:00
notable6 lizmat, 20 notes: https://gist.github.com/a30f53468e16743882deff43ca71c3b321:00
Geth ¦ rakudo: b11e856f3d | (Nick Logan)++ (committed using GitHub Web editor) | src/Perl6/World.nqp21:11
¦ rakudo: Remove redundant exception reporting 21:11
¦ rakudo: review: https://github.com/rakudo/rakudo/commit/b11e856f3d21:11
lizmat notable6: weekly reset21:18
notable6 lizmat, Moved existing notes to “weekly_2019-09-09T21:18:12Z”21:18
lizmat and another Perl 6 Weekly hits the Net: https://p6weekly.wordpress.com/2019/09/09/2019-35-6-ovid-trepidated/21:34
Xliff SmokeMachine: Using that gives the same error. See: say $*RED-DB.execute: "select * from poe21:45
*See: https://paste.fedoraproject.org/paste/E1dXRP2k4MJrMtiFILeTEQ21:46
tobs joined22:16
Ven`` left22:24
Ven`` joined22:24
Ven`` left22:24
Kaiepi left22:38
Xliff left22:39
Kaiepi joined22:39
SmokeMachine Xliff: your model has no columns...22:42
tellable6 SmokeMachine, I'll pass your message to Xliff22:42
Kaiepi left23:23
Kaypie joined23:23
SmokeMachine https://github.com/FCO/Red/wiki23:45
sorry, wrong channel23:45
lucasb left23:52

Logs Search ←Prev date Next date→ Channels Documentation