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
{{ message }}
This repository has been archived by the owner on Apr 13, 2023. It is now read-only.
The Language design Frequently Asked Questions¹ should cover our syntax of comma-separated conditions
if (existsa, nonemptyb)
since newcomers will naturally want to write
if (existsa && nonemptyb)
This could be added to the existing section Prefix form for is Type, exists, and nonempty (with a generalized title), or a new section below it. I vote for the former – I think that
the prefix form of these conditions,
the need for comma-separating them (ambiguity of exists x = a && b), and
the existence of and difference to their postfix forms, which do not need commas
should better be explained in a single section.
I can take a stab at this tomorrow.
¹ which, aside, would look much better as Language Design Frequently Asked Questions
The text was updated successfully, but these errors were encountered:
@lucaswerkmeister While if(! person is Employee){ ... } is valid syntax, it doesn't narrow down the type of person (what the whole point of conditions vs. expressions is). Maybe this is what was meant with the comment?
The Language design Frequently Asked Questions¹ should cover our syntax of comma-separated conditions
since newcomers will naturally want to write
This could be added to the existing section Prefix form for
is Type
,exists
, andnonempty
(with a generalized title), or a new section below it. I vote for the former – I think thatexists x = a && b
), andshould better be explained in a single section.
I can take a stab at this tomorrow.
¹ which, aside, would look much better as Language Design Frequently Asked Questions
The text was updated successfully, but these errors were encountered: