Re: Junctions now being stringified as one alternative per line?

Actually, Zoffix pointed out to me on IRC that it's a bug; say is supposed to call .gist on the Junction itself. Until that gets fixed, it's probably a good idea to use `say $foo.perl` or `put $foo.perl` instead. The justification is that `say` is often used "to dump iffy stuff that doesn't quite

Re: Junctions now being stringified as one alternative per line?

That was the behaviour before those commits. It was explicitly changed to how it works now, I believe. On 25/02/18 16:54, yary wrote: > Should "say" handle junctions and wrap them with ".gist?" Seems like > it ought to, but maybe that introduces problems. > > -y > > On Sun, Feb 25, 2018 at 11:48

Re: Junctions now being stringified as one alternative per line?

Should "say" handle junctions and wrap them with ".gist?" Seems like it ought to, but maybe that introduces problems. -y On Sun, Feb 25, 2018 at 11:48 AM, Timo Paulssen wrote: > That's right. Say will also call .gist on what you pass to it, but say > doesn't declare that it

Re: Junctions now being stringified as one alternative per line?

That's right. Say will also call .gist on what you pass to it, but say doesn't declare that it handles junctions, so before it can call .gist on what it gets, it will be handled by the auto-threader, so you'll get say, and therefor .gist, called on everything inside the junction and the result

Re: Junctions now being stringified as one alternative per line?

I don't have Rakudo handy, is the answer to "how to make junctions show as Sean expects" say $junction.gist ; ? -y On Sat, Feb 24, 2018 at 7:27 PM, Timo Paulssen wrote: > I'm pretty sure you're running up against this change in rakudo: > >

Re: Junctions now being stringified as one alternative per line?

I'm pretty sure you're running up against this change in rakudo: https://github.com/rakudo/rakudo/blob/master/docs/ChangeLog#L203 >     + Made print/say/put/note handle junctions correctly [07616eff] >    [9de4a60e][8155c4b8][3405001d] the relevant commits being:

Junctions now being stringified as one alternative per line?

I recently upgraded to Rakudo 2018.01 and just now encountered some perplexing behavior. Junctions, regardless of type, are being stringified one alternative per line. 1 & 2, 1 | 2, 1 ^ 2, and none(1, 2) are all displayed as a 1, a newline, and 2. Previously I would see eg. "all(1, 2)", which