We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Following https://www.vidarholen.net/~vidar/An_Empirical_Investigation_into_Programming_Language_Syntax.pdf there is a case to use:
is in place of = for definitions
is
=
as
not= in place of /=
not=
/=
The text was updated successfully, but these errors were encountered:
Should blocks have an explicit end?
In case of try..as, if..else, this could be useful
In case of function bodies, it would be a problem for one-liners and do-chains.
Sorry, something went wrong.
Use any instead of _?
any
_
if .. then ... else if .. then ... else ... >> xx
Should apply xx to the whole else..if block
Merge with https://github.com/xarvh/squarepants/wiki/Parser---Lexer-issues
No branches or pull requests
Following https://www.vidarholen.net/~vidar/An_Empirical_Investigation_into_Programming_Language_Syntax.pdf there is a case to use:
is
in place of=
for definitionsis
andas
(the formatter could accept both in record literals?)not=
in place of/=
The text was updated successfully, but these errors were encountered: