# New Ticket Created by  "Carl Mäsak" 
# Please include the string:  [perl #121310]
# in the subject line of all future correspondence about this issue. 
# <URL: https://rt.perl.org/Ticket/Display.html?id=121310 >


<Rotwang> okay, one more question, and I'll leave you guys alone [;
<Rotwang> p: True ~~ True
<camelia> rakudo-parrot 505868: OUTPUT«Potential difficulties:␤
Smartmatch against True always matches; if you mean to test the topic
for truthiness, use :so or *.so or ?* instead␤    at
/tmp/drk_UUShw0:1␤    ------> True ~~⏏ True␤»
<masak> Rotwang: smartmatching against True probably doesn't do what
you think it does.
<Rotwang> masak: this is what I get on R* 2014.1:
<Rotwang> > True ~~ True
<Rotwang> Null PMC access in get_string()
<masak> Rotwang: ouch, that Null PMC access is a new bug :/
<masak> can anyone else confirm it?
<FROGGS_> maybe a known REPL bug?
<Rotwang> masak: so True ~~ True should return true?
<masak> Rotwang: yes, $X ~~ True should return True.
<FROGGS_> masak: it NPMCAs in the REPL but not in -e
<FROGGS_> perhaps it can't stringify a .worry?
* masak submits rakudobug
<FROGGS_> masak: This is perl6 version 2014.02-15-g51d3cae built on
parrot 6.1.0 revision RELEASE_6_1_0
<FROGGS_> blead that is
<masak> gracias.
<FROGGS_> it does not fail using perl6-m though
<FROGGS_> (can't test perl6-j atm)
<masak> interesting. including that in the bug report.

Reply via email to