From @drforr

I'm not even sure if the error text is correct, come to think of it. I'd
think that a leading '=' outside of a here-doc or multi-line string
regardless of q/qq/Q<[[ variant should be treated as a POD comment, so I
would expect this error to read​:

=end without matching =begin FOO

or "Preceding context expects a term, but found infix = instead. Maybe
you wanted a matching '=begin FOO' POD comment earlier?"

--cut here--
=end FOO
--cut here--

--cut here--
===SORRY!=== Error while compiling /home/jgoff/bug.t
Preceding context expects a term, but found infix = instead
at /home/jgoff/bug.t​:1
------> =⏏end FOO
--cut here--

From @zoffixznet

On Mon, 01 Jun 2015 05​:41​:01 -0700, drforr@​pobox.com wrote​:

I'm not even sure if the error text is correct, come to think of it. I'd
think that a leading '=' outside of a here-doc or multi-line string
regardless of q/qq/Q<[[ variant should be treated as a POD comment, so I
would expect this error to read​:

=end without matching =begin FOO

or "Preceding context expects a term, but found infix = instead. Maybe
you wanted a matching '=begin FOO' POD comment earlier?"

--cut here--
=end FOO
--cut here--

--cut here--
===SORRY!=== Error while compiling /home/jgoff/bug.t
Preceding context expects a term, but found infix = instead
at /home/jgoff/bug.t​:1
------> =⏏end FOO
--cut here--

Thank you for the report. This is now fixed.

Fix​: rakudo/rakudo@2c951798a2162ce
Test​: rakudo/rakudo@2c951798a2162ce

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

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