From @AlexDaniel

Code​:
say �hello

Result​:
===SORRY!=== Error while compiling -e
Unable to parse expression in smart single quotes; couldn't find final "�"
at -e​:1
------> say �hello�<EOL>
  expecting any of​:
  argument list
  smart single quotes
  term

From this article https://en.wikipedia.org/wiki/Quotation_mark (perhaps not the best reference, but still)​:

�The "smart quotes" feature in some computer software can convert vertical quotation marks to curly ones�

�Curved and straight quotes are also sometimes referred to as smart quotes (���) and regular quotes ("�") respectively; these names are in reference to the name of a function found in several word processors that automatically converts straight quotes typed by the user into curved quotes, attempting to be "smart" enough to determine which typed quotes are opening and closing.�

There is nothing �smart� about these quotes in our case. In fact, I type these quotes directly and am somewhat pissed off by the message (these quotes did not get into my code accidentally because some software decided to change them).

I suggest to refer to them as �curly quotes�, this is perhaps the best way (other ways would be �book� and �typographic�, but again this is a bit off).

From @AlexDaniel

Done in rakudo/rakudo@0ba7733

I think a test will not hurt? For example, it can check that the word “curly” is in the error message. These series of tickets are focused on making things less confusing for newcomers if they stumble upon curly quotes, so I guess ensuring that we clearly indicate that these quotes are not regular is a good idea.

From @zoffixznet

On Sun, 04 Dec 2016 17​:20​:48 -0800, alex.jakimenko@​gmail.com wrote​:

Done in
rakudo/rakudo@0ba7733

I think a test will not hurt? For example, it can check that the word
�curly�
is in the error message. These series of tickets are focused on making
things
less confusing for newcomers if they stumble upon curly quotes, so I
guess
ensuring that we clearly indicate that these quotes are not regular is
a good
idea.

Tests added​: https://rt-archive.perl.org/perl6//Public/Bug/Display.html?id=130260

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

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