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
The following works, so perhaps it's only an issue with the shorthand form when using <~:
fnx->x+1end<~[1,2,3]
It's probably a separate issue, but I have had nested captures via & are not allowed errors whilst using Witchcraft when trying to chain (not nest) anonymous functions, which I've always resolved by using the fn ... end longhand form. Looking at the examples on various conference slides for the Witchcraft suite, I think this is a known issue and I assume it's to do with how it's shoehorned into Elixir.
Actually additional brackets fix behaviour. But result of expression without brackets is completely unexpected. It should be compilation error in my opinion (if it can't be fixed).
iex(1)>useWitchcraftWitchcraft.Comonadiex(2)>&(&1+1)<~[1,2,3]#Function<7.126501267/1 in :erl_eval.expr/5>iex(3)>(&(&1+1))<~[1,2,3][2,3,4]
fmap alias <~ is not working:
The text was updated successfully, but these errors were encountered: