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
At time of writing, APPLY will fill in NONE for unspecified arguments or refinements. It will also tolerate too many. So in the test suite, the following is expected to succeed:
1== apply func [a] [a] [12]
As APPLY is already somewhat brittle in terms of corresponding to the order in which refinements appear in the function spec, this "laxness" only makes it worse. It likely represents a misunderstanding or error. Raising an error would be preferable.
Actually, I found a use for APPLY being able to tolerate excess arguments. It is not true that it is always an error to supply more arguments. For an example, see #2193.
The text was updated successfully, but these errors were encountered:
Submitted by: fork
At time of writing, APPLY will fill in NONE for unspecified arguments or refinements. It will also tolerate too many. So in the test suite, the following is expected to succeed:
As APPLY is already somewhat brittle in terms of corresponding to the order in which refinements appear in the function spec, this "laxness" only makes it worse. It likely represents a misunderstanding or error. Raising an error would be preferable.
Imported from: CureCode [ Version: r3 master Type: Wish Platform: All Category: Unspecified Reproduce: Always Fixed-in:none ]
Imported from: metaeducation#2237
Comments:
Actually, I found a use for APPLY being able to tolerate excess arguments. It is not true that it is always an error to supply more arguments. For an example, see #2193.
The text was updated successfully, but these errors were encountered: