🦋 Welcome to the IRC channel of the core developers of the Raku Programming Language (raku.org #rakulang). This channel is logged for the purpose of history keeping about its development | evalbot usage: 'm: say 3;' or /msg camelia m: ... | log inspection situation still under development | For MoarVM see #moarvm
Set by lizmat on 22 May 2021.
Geth nqp: usev6++ created pull request #734:
[JVM] Let with/without use 'defined' 		05:23
lizmat notable6: weekly 11:40
notable6 lizmat, 3 notes: gist.github.com/e362d374b90039bf38...a88a0bdfd6
lizmat notable6: weekly reset 11:41
notable6 lizmat, Moved existing notes to “weekly_2021-08-16T11:41:23Z”
|Tux| Rakudo v2021.07-26-g289a62f4a (v6.d) on MoarVM 2021.07-18-g343d0f37f
csv-ip5xs0.845 - 0.881
csv-ip5xs-208.479 - 8.758
csv-parser27.298 - 27.594
csv-test-xs-200.370 - 0.371
test7.676 - 7.685
test-t1.909 - 2.004
test-t --race0.883 - 0.895
test-t-2033.011 - 33.765
test-t-20 --race9.484 - 9.993
 14:01
lizmat And yet another Rakudo Weekly News hits the Net: rakudoweekly.blog/2021/08/16/2021-...cumbering/ 14:12
sena_kun lizmat++ 14:17
lizmat PSA: log server will be down for a bit for server upgrades 16:03
Tux__ is(some-call(args),""|Str,'this call can return "" or Undefined Str') 16:05
→
Cannot unbox a type object (Str) to a str
is that counter-intuitive or did I go over the limit
lizmat how is Undefined defined ? 16:06
:-)
Tux__ an Str typed value with no content at all 16:07
like «Any» or «Str» 16:08
lizmat m: sub a(str $a) { }; a Str
camelia Cannot unbox a type object (Str) to a str.
in sub a at <tmp> line 1
in block <unit> at <tmp> line 1
lizmat that's what you're doing somewhere
Tux__ m: use Test; my Str $s;is($s,""|Str,"test") 16:11
camelia not ok 1 - test
# Failed test 'test'
# at <tmp> line 1
Cannot unbox a type object (Str) to a str.
in sub is at /home/camelia/rakudo-m-inst-2/share/perl6/core/sources/2D4A7CA10695CD2B374573413D261A660E282E2A (Test) line 211
in block <unit…
Tux__ that is what I was trying
lizmat is() assumes you pass it something that is a string 16:12
my Str $s is *not* a string, but a type object
Tux__ but, but ... 16:13
m: use Test; my Str $s="x";is($s,""|"x","test")
leont The error eventually comes from sub infix:<~>(Str:D $a, Junction:D $b)
camelia ok 1 - test
Tux__ Ahh, :D
leont It assumes the Junction eigenstates are all defined
Tux__ damn 16:14
thanks leont I now understand
leont I don't understand why it assumes that, or if that is a correct assumption
Tux__ I though that I was balancing the knive's edge again 16:15
lizmat m: use Test; is Str,""
camelia not ok 1 -
# Failed test at <tmp> line 1
# expected: ''
# got: (Str)
lizmat hmmm
leont I suspect it's correct not to accept it, but that the error is less than awesome
lizmat Tux__: use is-deeply vs is ? 16:17
Tux__ in this specific case I can be more strict by using Str instead of ""|Str. I was just curious where I went wrong given the two examples 16:18
lizmat PSA: server is up again 16:19
releasable6 Next release in ≈4 days and ≈23 hours. 1 blocker. Please log your changes in the ChangeLog: github.com/rakudo/rakudo/wiki/ChangeLog-Draft 19:00
Altai-man what 19:21
oh dammit
releasable6, status 19:26
releasable6 Altai-man, Next release in ≈4 days and ≈23 hours. 1 blocker. Changelog for this release was not started yet
Altai-man, Details: gist.github.com/d5d52ed0a2183c45bd...3022054eba

Powered by Cro and the Raku® Programming Language.

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

Thank you!