Thomas Refis

What @paurkedal said sounds correct to me indeed, the opam file of these packages should be fixed.

I'll let @xclerc or @diml look at the runtime dependency of `ppx_sexp_conv` on `base`.

I believe what @rgrinberg was referring to are some discussions from last summer (or the previous one?) about the compiler exposing errors as json objects, or something of the sort....

Given what's been said above, I'm not sure "Good first issue" is the right tag.

That is a limitation with the documentation generator (odoc) that we hope will be lifted soon (in a couple of weeks / months).

I have some examples where ocamlformated code goes beyond 80c, and it's not related to comments: ``` $ cat lambda/.ocamlformat profile=conventional if-then-else=k-r indicate-multiline-delimiters=closing-on-separate-line break-cases=all $ ocamlformat lambda/ocamlformat.ml let inline_lazy_force_cond arg...

Indeed, this is the same issue as #774 , and it's been a long standing one. I thought we had fixed it at some point, but apparently not (or it...

> It seems that even correct code is generating overlapping locations, both with Merlin and OCaml parsers: That's a known issue yes, there are a bunch of escape hatchs builtin...

FTR: the upstream PR has finally be merged. So 4.12 merlin might be a bit better when it comes to locations (but I'm still not sure what will happen in...

A developer's meeting focused on type system changes was held a couple of weeks ago during which this PR, but also the broader "modular implicits" project were discussed. Concurrently to...