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
I am looking to implement an array.any function that can be passed a function, which in many cases needs to be curried with additional arguments. For example:
Invalid number of arguments `1` passed to `string.contains '20'` while expecting `2` arguments
It appears that during parsing this is being treated as a function call to string.contains, instead of a function pointer plus additional arguments to the array.any function call
I tried using named arguments, but that does not help (i.e. array.any function: @string.contains args: '20')
I think the @ operator needs to be less greedy, to only capture the function itself (which may be from a member access), but to not parse as an actual function call, but not sure if this is intended / desired or if there is possibly a different workaround
The text was updated successfully, but these errors were encountered:
I think the @ operator needs to be less greedy, to only capture the function itself (which may be from a member access), but to not parse as an actual function call, but not sure if this is intended / desired or if there is possibly a different workaround
I am looking to implement an
array.any
function that can be passed a function, which in many cases needs to be curried with additional arguments. For example:This is using a function declared as:
Given the above an error is thrown:
It appears that during parsing this is being treated as a function call to string.contains, instead of a function pointer plus additional arguments to the
array.any
function callI tried using named arguments, but that does not help (i.e.
array.any function: @string.contains args: '20'
)I think the
@
operator needs to be less greedy, to only capture the function itself (which may be from a member access), but to not parse as an actual function call, but not sure if this is intended / desired or if there is possibly a different workaroundThe text was updated successfully, but these errors were encountered: