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
There are pegs with name source and target.
We call moveDirect with source source and with target target.
We call moveDirect with source source and with target target.
We want to be able to write, for the second call:
We call moveDirect with source and target.
The text was updated successfully, but these errors were encountered:
I'm not sure I like the original idea now that I think about it. Omitting the parameter names and making it dependant on order removes quite some clarity. However, we could achieve almost the same by allowing argument labels to be inferred from the name of the value.
For example, in JavaScript and TypeScript we can do:
In the scenario language, the following would be equivalent:
We call moveDirect with source and with target.
We call moveDirect with source source and with target target.
This slightly deviates from the syntax in the original proposal in that it requires an additional with before target. That avoids confusion when lists are involved.
In a similar manner, we could do away with the awkward duplication in with clauses as part of There Sentences:
There is a University uni.
There is a Student with name Alice and with uni uni.
There is a Student with name Alice and with uni.
Example:
Instead of the current:
We want to be able to write, for the second call:
The text was updated successfully, but these errors were encountered: