I think this is correctly classified as a feature, not a bug. I agree with Chiaroscuro that the current behavior isn’t broken. On the other hand:
- There’s a common pattern of user-error caused by the current syntax.
- There’s a straightforward-to-describe change that could let the computer, instead of the human, address that error.
- The change doesn’t appear to have any substantial negative effects.
(I acknowledge that a change like this would mean you can’t end a statement with two quotes, but I have never seen that done intentionally to the best of my knowledge, and other systems with similar behavior just strip one quote - so if you want to force a "
at the end of the say, you can do so by typing ""
- which is a little awkward, but now we’ve moved the awkwardness to the rare case of wanting double-quotations from the common case of not wanting them.)
So, I’d be in support of this as a feature. Which doesn’t mean the current way is broken, just that we could improve!