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
It is not a good practice that we change a name for a builtin type. Is it because the kind unknown is ambiguous from the type with a name of unknown and the case where there is an invalid kind which we do not know?
The text was updated successfully, but these errors were encountered:
Yeah that was the original thinking, and because it aligned more closely with what we got from m4. Happy to change this though, it will just be a breaking change that will have to be driven across languages
It is not a good practice that we change a name for a builtin type. Is it because the kind
unknown
is ambiguous from the type with a name ofunknown
and the case where there is an invalid kind which we do not know?The text was updated successfully, but these errors were encountered: