releasable6 Next release in ≈1 day and ≈15 hours. 4 blockers. Please log your changes in the ChangeLog: github.com/rakudo/rakudo/wiki/ChangeLog-Draft 03:00
lizmat Files=1305, Tests=111221, 205 wallclock secs (28.55 usr 8.23 sys + 2878.34 cusr 271.04 csys = 3186.16 CPU) 08:34
Geth rakudo: 296fbcf46f | (Ben Davies)++ | 2 files
Fix reflection for . twigilled parameters

A "$.foo" parameter would get stringified as "f.foo". There were two problems causing this:
  - . twigilled parameters' names were being reset unnecessarily by the
   compiler
  - Parameter.usage-name wasn't accounting for . twigils		 08:47
roast: d2ac6d0251 | (Ben Davies)++ | S06-signature/introspection.t
Add tests for attribute parameter naming
 09:04
[Tux] Rakudo version 2020.02.1-251-g296fbcf46 - MoarVM version 2020.02.1-50-g15e94eecb
csv-ip5xs0.702 - 0.737
csv-ip5xs-206.204 - 6.354
csv-parser24.431 - 25.461
csv-test-xs-200.390 - 0.395
test7.604 - 7.712
test-t1.973 - 2.039
test-t --race0.955 - 0.969
test-t-2031.749 - 31.999
test-t-20 --race9.629 - 10.314
 09:22
sena_kun releasable6, status 10:32
tellable6 2020-03-25T11:24:58Z #raku-dev <lizmat> sena_kun should we just start changing github.com/rakudo/rakudo/wiki/ChangeLog-Draft ? It seems to be for 2020.02 ?
releasable6 sena_kun, Next release in ≈1 day and ≈8 hours. 4 blockers. 166 out of 251 commits logged (⚠ 3 warnings)
tellable6 2020-03-26T11:19:43Z #raku-dev <lizmat> sena_kun updated the ChangeLog Draft with the commits that I had knowledge about
releasable6 sena_kun, Details: gist.github.com/5a8d9033225e1ab64d...095490ab68
sena_kun lizmat, thanks a lot for your changelog work! 10:33
lizmat sena_kun: yw 10:37
sena_kun Now appveyor builds are what's "fun". 10:38
Geth rakudo: a3f61d7667 | (Elizabeth Mattijsen)++ | 6 files
Apparently SEQUENCE *must* be a sub

In order to make pre-compilation of infiix<...> work. Fixes the problem Blin found with Array::Shaped::Console module.
Geth roast: cff9a0ed5b | (Elizabeth Mattijsen)++ | 3 files
Add test for precompiling infix:<...>
 11:04
roast: a51f7bf8d8 | (Elizabeth Mattijsen)++ | spectest.data
Make sure precompilation infix:<...> tests are run
lizmat TIL that &rand ... * is actually a valid sequence 13:45
m: dd &rand ... *
evalable6 (0.2016219927186479e0, 0.3831100064267069e0, 0.…
lizmat, Full output: gist.github.com/8acf2591846710f2f8...7e8316639e
lizmat hmmm... camelia is AWOL again? nine ?
jnthn lizmat: That's cute :) 13:53
I mean, rand xx * is neater, but :) 13:54
lizmat hmmm.. I wonder whether it would make sense for methods that do not use "self", to remove it from the local lexpad, and change the signature to skip the first argument? 14:56
nine What would happen when a derived class overrides that method and actually uses self? 14:59
lizmat nothing: that class method would have its own lexpad / argument receiving logic ? 15:00
jnthn lizmat: I'm pretty sure spesh actually discards the parameter instructions for an unused parameter anyway, and lexical to local lowering already happens on self so it should be able to see that it is unused 15:09
So I think this already falls out of stuff that is already done
Except it can do it for any parameter, not just self 15:10
Bit like how slurpy named parameter processing instructions also just vanish after specialization
(If unused)
Geth rakudo: 13ca677e93 | (Stefan Seifert)++ | src/core.c/CompUnit/PrecompilationStore/File.pm6
Fix CompUnit::PrecompilationUnit::File::bytecode not returning bytecode

Since commit 81ac37f88b294ef90b336562509d0cd51dc0c9a3 the bytecode method only returned the bytecode when it wasn't already initialized.		 15:12
nine Huh....apparently it's still broken 15:15
lizmat good catch! 15:16
I guess I was confusing it with nqp::unless semantics
m: use nqp; sub a() { nqp::unless(42,666) }; dd a 15:17
evalable6 42
lizmat nine: will look when back from cycling&
nine Still getting Type check failed for return value; expected Buf:D but got Slip (Empty) 15:19
Kaiepi ohh that sounds familiar 15:20
m: class FooHOW { method new_type() { my $meta := self.new; my Mu $obj := Metamodel::Primitives.create_type: $meta, 'Uninstantiable'; Metamodel::Primitives.configure_type_checking: $obj, (), :!authoritative; $obj }; method type_check(Mu, Mu \a) { say a } }; Metamodel::Primitives.is_type: 1, FooHOW.new_type 15:22
evalable6
Kaiepi m: class FooHOW { method new_type() { my $meta := self.new; my Mu $obj := Metamodel::Primitives.create_type: $meta, 'Uninstantiable'; Metamodel::Primitives.configure_type_checking: $obj, (), :!authoritative; $obj }; method type_check(Mu, Mu \a) { say a } }; Metamodel::Primitives.is_type: FooHOW.new_type, 1
evalable6
Kaiepi blegh
a little while ago when i tried to write a type_check method for a HOW its type_check method would always take Slip as its checkee, no matter what was being typechecked 15:23
Geth nqp: dbbe9e170d | (Daniel Green)++ | src/vm/moar/QAST/QASTOperationsMAST.nqp
Remove some unused variables
 15:27
Kaiepi looks like that's been fixed since i last tried 15:36
nine Oh it did help! I've just tested with raku instead of ./raku-m 15:38
make install helped
Kaiepi oh wait, i was forgetting to compose the type 15:42
type_check doesn't get called at all with Metamodel::Primitives.configure_type_checking($obj, (), :!authoritative)...?
lizmat m: dd "a",2 ... * # this feels like it should be an error 17:50
evalable6 ("a", 2, 1, 0, -1, -2, -3, -4, -5, -6, -7, -8, …
lizmat, Full output: gist.github.com/7c68ea8e2c12552658...7e3968a1a5
sena_kun releasable6, status 17:51
releasable6 sena_kun, Next release in ≈1 day and ≈1 hour. 3 blockers. 166 out of 253 commits logged (⚠ 3 warnings)
sena_kun, Details: gist.github.com/b0f2e5953d2070eefe...cf290c4f56
sena_kun anyone to look at github.com/rakudo/rakudo/pull/3572 sanity?
lizmat I would drop the "ask on the [email@hidden.address] mailing list" 17:53
that mailing list is pretty dead afaik
sena_kun fair enough
Geth rakudo/Altai-man-patch-1: 0123c6dcca | Altai-man++ (committed using GitHub Web editor) | tools/create-release-announcement.raku
Prefer irc channel over mailing list
 17:55
jnthn releasable6: status 17:57
releasable6 jnthn, Next release in ≈1 day and ≈1 hour. 3 blockers. 166 out of 253 commits logged (⚠ 3 warnings)
jnthn, Details: gist.github.com/4e5538ddf8b9b7ad12...6db4422384
sena_kun m: say 2 (cont) <1 2 3>; say 2 (elem) <1 2 3>; 18:46
evalable6 False
False
sena_kun shouldn't ^ evaluate to True? I mean, the array has IntStr and
m: say 2 ~~ IntStr.new(2);
evalable6 (exit code 1) Too few positionals passed; expected 3 arguments but got 2
in block <unit> at /tmp/XVxfQrn10n line 1
sena_kun sigh
m: say 2 ~~ <2>; 18:47
evalable6 True
sena_kun ^ evaluates to true
Geth rakudo: Kaiepi++ created pull request #3575:
Improve introspection of anonymous parameters		 18:59
roast: Kaiepi++ created pull request #630:
Update tests WRT changes to introspection of anonymous parameters		 19:00
lizmat sena_kun: Set semantics means that the .WHICH of objects are used 19:38
tellable6 lizmat, I'll pass your message to sena_kun
lizmat m: dd 1.WHICH, <1>.WHICH
evalable6 ValueObjAt.new("Int|1")
ValueObjAt.new("IntStr|1")
lizmat note that they are not the same
Geth rakudo: 87d2ff9536 | (Ben Davies)++ | src/core.c/Parameter.pm6
Fix Parameter.raku with OUTER default values

The parameter for a "{ $_ }" block was winding up with "OUTER::<$_?>" in its .raku instead of "OUTER::<$_>".		 19:40
roast: 399f33576f | (Ben Davies)++ | S06-signature/introspection.t
Add test for Parameter.raku with OUTER defaults
 19:45
patrickb o/ 20:30
I have a change in rakudo and MoarVM that depend on each other. So it breaks with either an older MoarVM or an older Rakudo. What's the policy with such changes? Is just bumping versions in nqp and Rakudo enough? 20:34
lizmat I think so, as quickly as possible :-) 20:50
AlexDaniel patrickb: if you want things to be even better, make sure that there's a bump before you commit your changes 21:33
this way your changes are isolated in a single bump
p6steve raku: say 3 21:52
evalable6 3
nine m: say "back" 22:48
camelia back
lizmat whee!
lizmat bisectable6: dd 1,2,3, * + 1 ...^ 7,14,28 ...^ * > 100 22:55
bisectable6 lizmat, Bisecting by output (old=2015.12 new=87d2ff9) because on both starting points the exit code is 1
lizmat committable6:dd 1,2,3, * + 1 ...^ 7,14,28 ...^ * > 100
committable6 lizmat, ¦dd: «Cannot find this revision (did you mean “all”?)»
lizmat committable6: dd 1,2,3, * + 1 ...^ 7,14,28 ...^ * > 100
committable6 lizmat, ¦dd: «Cannot find this revision (did you mean “all”?)»
lizmat committable6: 1,2,3, * + 1 ...^ 7,14,28 ...^ * > 100
bisectable6 lizmat, bisect log: gist.github.com/edfa8fb61d7c04ff8c...2c37a30a29 22:56
lizmat, (2016-06-09) github.com/rakudo/rakudo/commit/b6...430078bc7d
committable6 lizmat, ¦1,2,3, * (4 commits): «Cannot find this revision (did you mean “all”?)»
lizmat m: dd 1,2,3, * + 1 ...^ 7,14,28 ...^ * > 100 # this feels LTA
camelia Too many positionals passed; expected 2 arguments but got 3
in block <unit> at <tmp> line 1
travis-ci Rakudo build errored. Ben Davies 'Fix Parameter.raku with OUTER default values 22:58
travis-ci.org/rakudo/rakudo/builds/667858209 github.com/rakudo/rakudo/compare/1...d2ff953666
lizmat restarted the one failing job 22:59
releasable6 Next release in ≈19 hours. 3 blockers. Please log your changes in the ChangeLog: github.com/rakudo/rakudo/wiki/ChangeLog-Draft 23:00
AlexDaniel 6c: 1,2,3, * + 1 ...^ 7,14,28 ...^ * > 100 23:04
committable6 AlexDaniel, gist.github.com/cd14193e7272e9d54e...b79907b558

Powered by Cro and the Raku® Programming Language.

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

Thank you!