New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
{} are not brackets #2114
Comments
|
See irc discussion linked above. To avoid confusion it should always be “curly braces” and “square brackets” which is unambiguous. |
|
So the xt would check whether brackets is preceded by curly? |
|
Yes, something like:
|
I don't know, however, about closing the issue #2114. Several problems * We need a generic name that includes parentheses/braces/brackets * Do we need/want the test? It might include some verbosity * Sometimes parentheses (plural) is spelled parenthesis (singular).
|
Test added in There is currently no exception mechanism; if one is needed, let me know. |
|
Down to: These need to be reviewed; possible outcomes: add one of the words, rework to avoid the problem, or note that the text is correct as is and the test needs an exception/change. Looks like we could benefit from a word choice that means "any bracket or brace" |
|
27 ✔️ |
See http://colabti.org/irclogger/irclogger_log/perl6?date=2018-06-22#l377
We should make sure we are not referring to
{}as “brackets”, and maybe we can even add a test to guarantee that this doesn't happen in the future.The text was updated successfully, but these errors were encountered: