From sirrobert@gmail.com

15​:08 < sirrobert> r​: use Test; my Str $str; is_deeply {b=>2}, {a=>$str,
b=>2}, "wat";
15​:08 <+p6eval> rakudo 7d6aa0​: OUTPUT«not ok 1 - wat␤# got​: {"b" =>
2}␤# expected​:
  {"a" => Str, "b" => 2}␤»
15​:08 < sirrobert> r​: use Test; my Str $str; is_deeply {a=>$str, b=>2},
{a=>$str, b=>2}, "wat";
15​:08 <+p6eval> rakudo 7d6aa0​: OUTPUT«use of uninitialized value of type
Str in string
  context in sub is_deeply at lib/Test.pm​:217␤␤use of
uninitialized value
  of type Str in string context in sub is_deeply at
lib/Test.pm​:217␤␤ok 1 -
  wat␤»
15​:09 < sirrobert> It can handle the sad path ok, but not the happy?
15​:11 < masak> it definitely shouldn't emit a warning from within is_deeply
like that.
15​:11 < masak> please submit a rakudobug.

From @coke

On Mon Sep 24 12​:14​:29 2012, sirrobert@​gmail.com wrote​:

15​:08 < sirrobert> r​: use Test; my Str $str; is_deeply {b=>2}, {a=>$str,
b=>2}, "wat";
15​:08 <+p6eval> rakudo 7d6aa0​: OUTPUT«not ok 1 - wat␤# got​: {"b" =>
2}␤# expected​:
{"a" => Str, "b" => 2}␤»
15​:08 < sirrobert> r​: use Test; my Str $str; is_deeply {a=>$str, b=>2},
{a=>$str, b=>2}, "wat";
15​:08 <+p6eval> rakudo 7d6aa0​: OUTPUT«use of uninitialized value of type
Str in string
context in sub is_deeply at lib/Test.pm​:217␤␤use of
uninitialized value
of type Str in string context in sub is_deeply at
lib/Test.pm​:217␤␤ok 1 -
wat␤»
15​:09 < sirrobert> It can handle the sad path ok, but not the happy?
15​:11 < masak> it definitely shouldn't emit a warning from within is_deeply
like that.
15​:11 < masak> please submit a rakudobug.

02​:04 <[Coke]> r​: use Test; my Str $str; is_deeply {b=>2}, {a=>$str, b=>2},
  "wat";
02​:04 <camelia> rakudo bfd850​: OUTPUT«not ok 1 - wat␤# got​: {"b" => 2}␤#
  expected​: {"a" => Str, "b" => 2}␤»
02​:05 <[Coke]> r​: use Test; my Str $str; is_deeply {a=>$str, b=>2}, {a=>$str,
  b=>2}, "wat";
02​:05 <camelia> rakudo bfd850​: OUTPUT«ok 1 - wat␤»

Fixable with tests.

--
Will "Coke" Coleda

The RT System itself - Status changed from 'new' to 'open'

From @coke

On Fri May 10 23​:07​:20 2013, coke wrote​:

Fixable with tests.

Er, I mean closable.

--
Will "Coke" Coleda

From @usev6

This fails now with a typed exception "X​::Syntax​::ArgFlattener".

$ perl6 -e 'say(|(|([4])))'
===SORRY!=== Error while compiling -e
Arg-flattening | is only valid in an argument list
at -e​:1
------> say(|(|⏏([4])))

Please not that the first '|' is valid (argument list for 'say')​:

$ perl6 -e 'say(|([4]))'
4

I added a test to S32-exceptions/misc.t with commit Raku/roast@3c982d5b9e

I'm closing this ticket as 'resolved'.

@usev6 - Status changed from 'open' to 'resolved'

From @usev6

This fails now with a typed exception "X​::Syntax​::ArgFlattener".

$ perl6 -e 'say(|(|([4])))'
===SORRY!=== Error while compiling -e
Arg-flattening | is only valid in an argument list
at -e​:1
------> say(|(|⏏([4])))

Please note that the first '|' is valid (argument list for 'say')​:

$ perl6 -e 'say(|([4]))'
4

I added a test to S32-exceptions/misc.t with commit Raku/roast@3c982d5b9e

I'm closing this ticket as 'resolved'.

From @usev6

Erm, I'm very sorry. I closed the wrong ticket (and also hit the 'Update Ticket' button twice).

I'm re-opening this ticket.

@usev6 - Status changed from 'resolved' to 'open'

From @usev6

I added tests for the output of the above examples of 'is_deeply' to S24-testing/3-output.t with commit Raku/roast@5a9c4e27ab

The test file S24-testing/3-output.t is not yet in Rakudo's t/spectest.data, therefore I'm leaving this ticket open.

From @coke

On Thu Apr 09 12​:05​:44 2015, bartolin@​gmx.de wrote​:

I added tests for the output of the above examples of 'is_deeply' to
S24-testing/3-output.t with commit
Raku/roast@5a9c4e27ab

The test file S24-testing/3-output.t is not yet in Rakudo's
t/spectest.data, therefore I'm leaving this ticket open.

Added test file to spec test run, closing ticket.

--
Will "Coke" Coleda

@coke - Status changed from 'open' to 'resolved'