Florian Angeletti

gentle ping? @madroach would you prefer if I took care of rebasing the PR and updating the Change entry?

The third case only raises a warning when `Levent` are inserted (by `ocamlc -g` ), isn't ?

It is bit disturbing that some of those warnings only exists while compiling with `ocamlc -g`. What would be the effect of discarding `Levent` in all cases (beyond getting right...

My summary of the issue is that before 4.13 `|>` and `@@` were accidentally better behaved than standard applications when compiling with `ocamlc -g`. It seems fine to align the...

Given a value `E x`, the sub-expression `x` is certainly polymorphic, since it could be any type. At the same time, for existentially quantified type, we have a useful naming...

Under the hypothesis that this happen infrequently, maybe the more explicit `

The error is precisely that you are trying to apply the string indexing operator `.[]` to `(fun i -> i +1)` which is not a string. A code formatter tool...

Type error messages report conflicts between the types of various part of your program. When you are trying to apply the string indexing operator to a function, there is a...

OCaml syntax is white space insensitive: white spaces are always allowed between tokens. From that point of view, the expression `x . A.Very.Long.Path.field` is not different from `x = A.Very.Long.Path.value`.

Because they are both infix operators? Why should they follow different rules?