18:59 <d_bot> <EduardoRFS> it will, this is not really weird if you think how the typing order works, but yes this cases will be solved

21:38 <d_bot> <RegularSpatula> I’m not sure what you mean about the typing order honestly…do you know off the top of your head any links/refs talking about it ?

21:49 <d_bot> <EduardoRFS> sorry nope, but the typing order in OCaml matters, that's also why `let pat = e1 in e2` isn't the same as `match e1 with | pat -> e2`

21:51 <d_bot> <RegularSpatula> Huh, that’s interesting…I’ll have to look more into it

21:53 <d_bot> <leviroth> I don't think this is really about typing order (the way that type-directed disambiguation of constructors is).

21:55 <d_bot> <leviroth> I think the crux is that optional arguments get eliminated from the type of a function when it's applied, and not when it's passed in as an argument to another function. So if you have a higher-order function that expects an argument of type `foo -> bar` you can't pass it an argument of type `?baz:baz -> foo -> bar`.

21:58 <d_bot> <leviroth> And (prior to 4.13, and in the absence of ppx transformations) `|>` and `@@` are just higher-order functions.