I was completely wrong in assuming that .WHY returned a Str. So this probably is a bug, but for someone else to fix, as I’m a complete pod 6 noob.
Liz ============== > On 18 Dec 2015, at 12:24, Lloyd Fournier <lloyd.fo...@gmail.com> wrote: > > Hey Liz, > > The thing is that it seems that it isn't pod at any level. It simply isn't > parsed as pod. I'm out atm but when I was looking at it it was just parsed as > a quoted string and shoved into Pod::Block::Declarator. > > I would love to be wrong :) > > LL > > > On Fri, 18 Dec 2015 at 9:49 PM, Elizabeth Mattijsen via RT > <perl6-bugs-follo...@perl.org> wrote: > > On 18 Dec 2015, at 04:34, Lloyd Fournier (via RT) > > <perl6-bugs-follo...@perl.org> wrote: > > > > # New Ticket Created by Lloyd Fournier > > # Please include the string: [perl #126954] > > # in the subject line of all future correspondence about this issue. > > # <URL: https://rt.perl.org/Ticket/Display.html?id=126954 > > > > > > > #| look it's a C<thing>! > > sub thing { ... } > > > > say &thing.WHY.contents.perl; > > > > #-> ["look its a C<thing>"] > > Feels like ENOTABUG to me. > > What does “parse as POD” even mean in this context? It’s a string that > *could* be interpreted as pod. But it’s still just a Str. It’s entirely up > to you what you do with it. Standard tools will use it *as* pod, yes. But > at the .WHY level, it’s just a Str. > > > Well, anyway, that’s my interpretation of it :-) > > > > Liz >
