…test this in the sanity test
After thinking about it a bit more, I'm of the opinion that $version.Str should produce a string that doesn't include a leading 'v'. The .gist form does have a leading 'v', however, so C< say $version > still does what one expects. When putting a version in the middle of a string we'll often want to exclude any leading 'v' (e.g., when generating filenames), it's much easier to add a 'v' when it's needed than it is to eliminate one we don't want. Also, the form without the leading 'v' is the only one that can (so far) reliably have much chance of round-tripping back into Version.new(...), since alphabetics in strings arguments to Version.new are meaningful. At the moment the spec is somewhat silent on this topic, so I'm hoping this will make more sense. If not, a spec clarification or some official tests will let us know how to improve it. :-)
… the invocant.
… it if needed.
Also aligns closer to STD.pm6.
mostly so that .WHAT gives the full name Now without infinite recursion in the backtrace printer (contains a workaround for RT #114034)
This reverts commit 138213a. On my system it causes S02-literals/autoref.t and S02-literals/pairs.t to each run for over two minutes (consuming a fair bit of memory), and halts the rest of the spectest process.