> $zot **= ^foo # "what's that binary op doing there.. > # ..oh, that's a placeholder" I think this is a valid way of looking at it. If you think about it, * for typeglobs is the same symbol as * for multiplication. But the parser can figure it out based on context. I don't see any reason why it wouldn't be able to do the same for ^. -Nate
- Re: Different higher-order func notation? (was Re: RFC 23 (v... Jeremy Howard
- Re: Different higher-order func notation? (was Re: RFC ... Mike Pastore
- Re: Different higher-order func notation? (was Re: ... Nathan Wiger
- Re: Different higher-order func notation? (was ... Jeremy Howard
- Re: Different higher-order func notation? (... John Porter
- Re: Different higher-order func notation? (was ... Damian Conway
- Re: Different higher-order func notation? (was ... Mike Pastore
- Re: Different higher-order func notation? (was ... John Porter
- Re: Different higher-order func notation? (was Re: ... Ken Fox
- Re: Different higher-order func notation? (was ... Mike Pastore
- Re: Different higher-order func notation? (... Nathan Wiger
- Re: Different higher-order func notation? (... Ken Fox
- Re: Different higher-order func notation? (... Jeremy Howard
- Re: Different higher-order func notation? (... Ken Fox
- Re: Different higher-order func notation? (... Mike Pastore
- Re: Different higher-order func notation? (... Jeremy Howard
- Re: Different higher-order func notation? (... Nathan Wiger
- Re: Different higher-order func notation? (... Damian Conway
- Re: Different higher-order func notation? (... Jeremy Howard
- Re: Different higher-order func notation? (... Damian Conway
- Re: Different higher-order func notation? (... Jeremy Howard