From @moritz

11​:18 < jaffa4> rakudo​: print 1|2|3;
11​:18 <+p6eval> rakudo 3bd91f​: OUTPUT«This type cannot unbox to a native
  string␤ in method print at src/gen/CORE.setting​:6381␤
  in sub
  print at src/gen/CORE.setting​:6252␤ in block <anon> at
  /tmp/I_61q5dNjv​:1␤␤»

Should either autothread, or stringify the junction as a whole

From @FROGGS

still the same​:

<FROGGS> rakudo​: print 1 | 2 | 3;
<p6eval> rakudo bf472b​: OUTPUT«This type cannot unbox to a native
string␤ in method print at src/gen/CORE.setting​:7644␤ in sub print at
src/gen/CORE.setting​:7454␤ in block at /tmp/xB1f5M7g6V​:1␤␤»

but this is a related/new bug ($v shouldnt be visible)​:
<FROGGS> rakudo​: print (1 | 2 | 3).WHAT;
<p6eval> rakudo bf472b​: OUTPUT«use of uninitialized variable $v of type
Junction in string context in block at /tmp/iA1JwAYkxB​:1␤␤»

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

From @jnthn

On Wed Apr 11 02​:22​:30 2012, moritz wrote​:

11​:18 < jaffa4> rakudo​: print 1|2|3;
11​:18 <+p6eval> rakudo 3bd91f​: OUTPUT«This type cannot unbox to a native
string␤ in method print at src/gen/CORE.setting​:6381␤
in sub
print at src/gen/CORE.setting​:6252␤ in block <anon> at
/tmp/I_61q5dNjv​:1␤␤»

Should either autothread, or stringify the junction as a whole

The root of the trouble is that .Str auto-threaded, meaning that it gave
back another Junction, not a Str. Fixed that, and now​:

print 1|2|3;
any(1, 2, 3)>

So, tagging testneeded.

/jnthn

From @moritz

Tested in the ever-growing S03-junctions/misc.t

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