Currently, an identifier beginning with a u, followed by one or more digits, then followed by one or more valid identifier characters, [a-zA-Z_-][a-zA-Z0-9_-]*, is illegal. To give a concrete example, this could be a name like u123hello_world. Pre-2.1, with the original parser would give the following error:
error: Expected whitespace or a close parens. Found: 'hello_world'
An argument could be made to maintain this same behavior, to avoid confusion with unsigned integers, or to allow this type of name in a future version of Clarity.
Currently, an identifier beginning with a
u
, followed by one or more digits, then followed by one or more valid identifier characters,[a-zA-Z_-][a-zA-Z0-9_-]*
, is illegal. To give a concrete example, this could be a name likeu123hello_world
. Pre-2.1, with the original parser would give the following error:After 2.1, the parser gives the following error:
An argument could be made to maintain this same behavior, to avoid confusion with unsigned integers, or to allow this type of name in a future version of Clarity.