00:03 Altai-man_ joined 00:05 sena_kun left 00:11 patrickb left 00:24 Altai-man_ left
samcv is anyone against having rakudo have a text description in a Proc exception for signals? like SIGKILL is one signal that can cause it to throw if it's not sunk. 00:36
I was considering adding that. atm it just will tell you a number of the signal it got, which is not too helpful
tbrowder any objections to merging my Rakudo PRs 3310, 3260, or 3253? 01:57
02:25 ZzZombo left 02:34 Kaiepi left, ZzZombo joined 02:35 Kaiepi joined 02:59 ZzZombo left 03:13 ZzZombo joined 07:24 robertle joined 08:09 MasterDuke joined 09:25 sena_kun joined
nine patrickb: please don't change release file names just for esthetic reasons. There are scripts used by packagers that expect a certain naming scheme 09:54
tellable6 nine, I'll pass your message to patrickb
nine AlexDaniel: btw. I love this tellable6 feature ^^^ 09:55
10:02 Altai-man_ joined 10:05 sena_kun left
AlexDaniel nine: yeah. I like when you don't need to know the right command. Another example: 10:13
patrickb:
hmm… doesn't work :)
tellable6: patrickb 10:14
tellable6 AlexDaniel, I saw patrickb 2019-11-22T23:08:53Z in #raku-dev: <patrickb> Have a good sleep!
AlexDaniel ok yeah, I guess that makes sense
11:14 robertle left 11:24 robertle joined
lizmat m: (-> @a[3] { dd MY::.keys })(my @b[3] = <a b c>) # looks like a 3-element array *is* accepted in a signature, but then incorrectly stored in the lexpad 11:25
camelia ("\@a[3]", "\$_", "\$*DISPATCHER").Seq
lizmat bisectable6: (-> @a[3] { dd MY::.keys })(my @b[3] = <a b c>) 11:40
bisectable6 lizmat, Bisecting by output (old=2015.12 new=ed8f514) because on both starting points the exit code is 0
lizmat, bisect log: gist.github.com/eb9286e70c779d582a...578cb78990
lizmat, (2017-02-22) github.com/rakudo/rakudo/commit/1c...24e4d0d5d3
AlexDaniel 6c: (-> @a[3] { dd MY::.keys })(my @b[3] = <a b c>) 11:49
committable6 AlexDaniel, gist.github.com/fc94fc4b106352d591...f92c773744 11:50
lizmat yeah, since like ever :-)
12:03 sena_kun joined 12:05 Altai-man_ left
Geth rakudo: 26f63ff73e | (Tom Browder)++ | 2 files
Improve error msgs: invalid open bracket, declarator blocks

Modified embedded declarator block token to throw a better exception message.
Added another line to an existing exception message to direct the user to the possibility of an improper open bracket for a declarator block. ... (15 more lines)		 12:08
rakudo: bbcc342b41 | (Tom Browder)++ (committed using GitHub Web editor) | 2 files
Merge pull request #3253 from tbrowder/decl-blocks

Improve error msgs: invalid open bracket, declarator blocks
rakudo: 9a4c83afaa | (Tom Browder)++ | src/Perl6/Grammar.nqp
Allow user to retain formatting of pod leading declarator blocks

Allows the user to define an enviroment variable of
  'RAKUDO_POD_DECL_BLOCK_USER_FORMAT' that keeps user formatting of pod
leading declarator blocks instead of them being collapsed into a normalized string which is the current default.
... (14 more lines)		 12:09
rakudo: e03f013477 | (Tom Browder)++ (committed using GitHub Web editor) | src/Perl6/Grammar.nqp
Merge pull request #3260 from tbrowder/decl-fmt-user

Allow user to retain formatting of pod leading declarator blocks
tbrowder .ask jnthn any objections to PR #3310? 12:12
tellable6 tbrowder, I'll pass your message to jnthn
12:51 maettu joined 12:52 lucasb joined 13:24 travis-ci joined
travis-ci Rakudo build failed. Tom Browder 'Merge pull request #3253 from tbrowder/decl-blocks 13:24
travis-ci.org/rakudo/rakudo/builds/615949538 github.com/rakudo/rakudo/compare/e...cc342b41d0
13:24 travis-ci left 14:02 Altai-man_ joined 14:04 sena_kun left
masak greetings 14:15
I've been getting back into Perl 5 recently
it's been going well, but... I just found that this is not a valid thing to write in Perl 5: 14:16
`if ((my $x = 5) == 5 && $x > 2) {}`
I am so upset right now :)
TimToady isn't even here so I can slap him with a large trout of 20-20 hindsight 14:17
s/so I can/for me to/ 14:18
14:18 Voldenet left
masak moritz: <3 14:20
moritz: I still find bugs in the same way, but I don't have the focus/time to minimize them and report them, nor the time for frolicking play that tends to precede bug finding 14:21
nine I'm kinda considering making Distribution::Resource.Str blow up. I can't think of a good use for that method and it seems to be abused widely in connection with NativeCall 14:26
masak nine: what are those abuses? I'm curious.
and what'd be the correct use?
nine As in: my constant LIBLINENOISE = %?RESOURCES<libraries/linenoise>.Str; our sub linenoiseHistoryAdd(Str $line) is native(LIBLINENOISE) is export { * } 14:27
14:27 Voldenet joined, Voldenet left, Voldenet joined
nine This will cause the full absolute path to liblinenoise.so from the repository to be part of the precomp file. This in turn breaks when that precomp file gets moved, e.g. when it's created using the Staging repository during packaging and installed by copying the resulting file into the appropriate destination. 14:28
masak ah.
subtle.
nine There's absolutely no reason for that .Str call there. One can just remove it and the packaging issue will be solved.
masak not sure it merits a blowup, but certainly a warning, yes.
nine Sadly that still wont prevent crazyness like: github.com/hoelzro/p6-linenoise/bl...pm6.in#L15 14:30
People seem to believe, that one needs to do crazy stunts to achieve trivial things with regards to NativeCall. 14:31
masak sounds like an education problem more than anything else
how to raise all boats? :)
masak glares at p5 sigil variance 14:35
nine I don't understand how people even come up with that .Str. There's nothing about it in the docs. There's plenty of bad and wrong advise in the docs, but not this. 14:50
14:57 ExtraCrispy joined
masak users are the worst :P 14:59
tbrowder can someone please walk me through reverting my PR #3260 which now fails testing? (or revert it yourself). 15:08
oops, that should be PR #3253 15:09
16:04 sena_kun joined 16:05 Altai-man_ left
Geth ¦ problem-solving: JJ assigned to AlexDaniel Issue Harassment by another member of the community github.com/perl6/problem-solving/issues/131 16:14
AlexDaniel lizmat: mind if I assign you to that issue? I'm definitely not the role model when it comes to this 16:20
lizmat: or can you recommend somebody who can untangle this?
Geth ¦ problem-solving: lizmat self-assigned Harassment by another member of the community github.com/perl6/problem-solving/issues/131 17:29
¦ problem-solving: lizmat unassigned from AlexDaniel Issue Harassment by another member of the community github.com/perl6/problem-solving/issues/131 17:30
japhb nine: hoelzro may have written that before NativeCall did the necessary magic. It looks like that code was written ~4.5 years ago, and I vaguely recall lib-finding to be pretty hackish back then. 17:47
lizmat jmerelo: please privmsg me when you have a chance 17:53
tellable6 lizmat, I'll pass your message to jmerelo
lizmat afk&
tobs japhb: that specific part was written 2 days ago according to git blame. 17:59
japhb tobs: The block was written April 2015. It has just been patched over and over since then. 18:00
tobs oho 18:01
18:02 Altai-man_ joined 18:05 sena_kun left 18:10 ExtraCrispy left
dogbert17 releasable: next 18:44
releasable6 dogbert17, Next release will happen when it's ready. There are no known blockers. 248 out of 483 commits logged (⚠ 9 warnings)
dogbert17, Details: gist.github.com/0513d173481aece23a...efd70ffea0
AlexDaniel dogbert17: I'm on it, thanks :) 18:53
nine japhb: all the more reason to remove that code for good 19:08
japhb nine: Oh, I wasn't saying it shouldn't be removed/replaced, rather that we can't assume it was unnecessary *at the time*, and it's likely that a lot of the other cases of "doing things the hard/wrong way" for Nativecall bits are cargo culting from earlier modules that needed it at the time they were written. 19:13
19:15 Xliff joined
vrurg AlexDaniel: ping? 19:33
AlexDaniel pong
vrurg On github it'd take too much time. :) I don't like squashing because it actually means squashing everything. 19:34
Maybe I'd make another PR specifically for the release branch?
It would be totally same as I'd just branch off the current PR. 19:35
AlexDaniel vrurg: why not squash everything? 19:41
vrurg: the PR currently includes a bunch of irrelevant commits 19:42
like multiple submodule updates
and even the implementation was going back and forth with raku/rakudo changes 19:43
vrurg AlexDaniel: call it 'religious prejudice'. I'd like to keep the history.
submodule updates could be squashed, that I thought about.
AlexDaniel you can keep the history in your local branch, and squash things for the PR :) 19:44
I don't really need you to rebase it for the release branch, I can probably cherry-pick on my own, I just don't like the clutter
but every single commit will be doubled in history 19:45
which is not too bad if there are only a few, but 14…
surely some commits can be separate, like the RAKU_HOME one 19:46
vrurg AlexDaniel: that's why I propose a separate PR. The release branch is a dead-end, it'd be ok to have alternate history with it.
AlexDaniel but “Fix another Raku-style mistype” is just clutter :)
vrurg: it's not a dead-end 19:47
release branch will be merged back to master
AlexDaniel shower &
vrurg Oops... I forgot about the merge back.
Ok, let's see how many of them I can get squashed. 19:48
19:58 Geth_ joined, Geth left 20:03 sena_kun joined
AlexDaniel vrurg: you can also rebase it on top of the release branch 20:04
vrurg: then we can merge it into the release branch, and merge the release branch into master 20:05
20:05 Altai-man_ left
AlexDaniel ta-daa, every commit will exist only once :) 20:05
vrurg This one I like better. 20:06
I would still squash submodule updates and the 'fix', but otherwise it'd then remain as is. 20:07
20:17 EuAndreh[m] joined
Xliff m: package ReExport { role ReExportable {}; multi sub trait_mod:<is> (Mu \var, :$re-export!) is export { var does ReExportable }; }; package B { import ReExport; sub a is export is re-export { 'a' }; }; 20:23
camelia 5===SORRY!5=== Error while compiling <tmp>
Can't use unknown trait 'is' -> 're-export' in a sub declaration.
at <tmp>:1
expecting any of:
rw raw hidden-from-backtrace hidden-from-USAGE pure default
DEPRECATED inlinabl…
Xliff How do I import inlined packages?
vrurg AlexDaniel: not sure about the result of the rebase 20:40
AlexDaniel vrurg: that's wrong, yes 20:43
vrurg: basically you needed to take your commits and put them on top of the release branch 20:44
vrurg: which you sorta did, but you brought other commits with it
btw I really enjoyed this thing at the time: learngitbranching.js.org/ 20:45
it gives some nice exercises on how to juggle with commits 20:46
vrurg Leaving it as one more opened tab hoping will have time for it later. :) 20:50
Thanks! 20:52
AlexDaniel: done. 20:56
5 commits, release-2019.11 based. Looks like we gonna have raku binary. :) 20:57
AlexDaniel and the commit history looks clean! Thank you!
vrurg: btw have you seen this? github.com/rakudo/rakudo/issues/3313 20:58
20:59 maettu left
Geth_ rakudo/release-2019.11: 6 commits pushed by (Vadim Belman)++, (Aleks-Daniel Jakimenko-Aleksejev)++ 21:01
Xliff Woi? There is a 2019.11 release?
AlexDaniel Xliff: hold your horses
Xliff :(
Xliff slaps AlexDaniel with a horny wombat... 21:02
AlexDaniel :D
Xliff I haz no horses... only w0mb4ts
AlexDaniel pretty sure that wombat didn't consent
vrurg AlexDaniel: Yes, just saw an email about it.
Xliff :P
AlexDaniel there will be a release tomorrow-ish
Geth_ ¦ rakudo: vrurg self-assigned Missing tab github.com/rakudo/rakudo/issues/3313
AlexDaniel vrurg: I don't know which targets are affected and whether that issue is on the release branch, but if it is, you can commit it there directly 21:03
Xliff Ahh. I can hold the rest of the w0mb4t swarm, then.
vrurg AlexDaniel: makes sense. It would affect people upgrading from old releases. 21:04
It breaks clean up of outdated files. :(
Geth_ rakudo/release-2019.11: 3ac6cca3d1 | (Vadim Belman)++ | tools/lib/NQP/Config/Rakudo.pm
Add missing tabulation in a receipe line

Fix for rakudo/rakudo#3313. Was breaking cleanup of outdated files when upgrading from old releases.		 21:07
vrurg AlexDaniel: when do you plan to merge back to master? 21:08
AlexDaniel vrurg: 10 seconds ago 21:09
Geth_ rakudo/master: 8 commits pushed by (Vadim Belman)++, (Aleks-Daniel Jakimenko-Aleksejev)++
vrurg That was QUICK! ;) Ok, have some other stuff to do. 21:10
.ask jnthn Just would like to remind you to review final changes in R#3199 and R#3272 when you have time. Sorry for bothering, but 3199 is rather big and I'd like to avoid possible merge conflicts. 21:12
tellable6 vrurg, I'll pass your message to jnthn
21:31 lucasb left 21:46 Kaiepi left 21:47 Kaiepi joined 21:48 Kaiepi left
Xliff R#3199 21:53
reportable: R#3199
reportable6 Xliff, I cannot recognize this command. See wiki for some examples: github.com/perl6/whateverable/wiki/Reportable
AlexDaniel github.com/rakudo/rakudo/pull/3199
22:03 Altai-man_ joined 22:05 sena_kun left 22:49 Kaiepi joined 23:59 Altai-man_ left

Powered by Cro and the Raku® Programming Language.

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

Thank you!