You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would expect the second example to parse since it's a valid path. I think the meta parsing code does a lookahead expecting only a literal or an identifier, but paths can start with the non-identifier ::.
I read the previous discussion about not wanting Meta to have to cover all possible attribute syntaxes, but I think this fits solidly within the current expectations of what Meta should parse. Given that it stores Paths, it should be able to parse any kind of Path.
The text was updated successfully, but these errors were encountered:
Minimal reproduction:
I would expect the second example to parse since it's a valid path. I think the meta parsing code does a lookahead expecting only a literal or an identifier, but paths can start with the non-identifier
::
.I read the previous discussion about not wanting
Meta
to have to cover all possible attribute syntaxes, but I think this fits solidly within the current expectations of whatMeta
should parse. Given that it storesPath
s, it should be able to parse any kind ofPath
.The text was updated successfully, but these errors were encountered: