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
Currently in the LRM, errors are defined like this:
error e = error( ... );
Since this looks a lot like instantiating an object, might it make sense to put the new keyword before the error (to keep continuity across the language), and potentially capitalize Error
error e = new error( ... );
or
Error e = new Error( ... );
@rapid-lang/owners
The text was updated successfully, but these errors were encountered:
Dan and I are wondering what y'all think:
Currently in the LRM, errors are defined like this:
Since this looks a lot like instantiating an object, might it make sense to put the
new
keyword before the error (to keep continuity across the language), and potentially capitalizeError
or
@rapid-lang/owners
The text was updated successfully, but these errors were encountered: