Konstantin A. Olkhovskiy

Glancing at output of `ocamlc -dparsetree` for both refmt printed .mli and hand-written .mli with semantically same content, there is difference in `Psig_attribute`, for native hand-written comment it's `"ocaml.text"` while...

In case it's important, I'm using OCaml 4.06.0.

For others running into this issue: workaround to get docs done: ```reason [@ocaml.text " {1 Overview} This module implements "]; /** This is some type t */ type t; /*...

I believe that has nothing to do with Reason. `ocaml.text` is floating module level documentation, while `/** ... */` that is attached to certain ast nodes is `ocaml.doc`, and the...

Badge with npm release version is a great solution! I also typically look at releases tab in a github repo to check what's the latest release, that's indeed a pretty...

There isn't any particular workflow, you just put a tag on corresponding commit that you build your release from. This makes it trivial to build specific release from source if...

What about discussion in BuckleScript/bucklescript#1326? Citing proposed solution below: ```ocaml let [@bs] v0 = promise0 in (* default to Promise.bind *) let [@bs] v1 = promise1 in let [@bs Option]...

Just tried an example from [Let+ syntax backported to OCaml >= 4.02](https://discuss.ocaml.org/t/let-syntax-backported-to-ocaml-4-02/344) post with OCaml 4.08.1 and Reason 3.5.0 @ 8ee1ff66, got not-so-user-friendly "Unknown error": ``` $ refmt --parse=ml open...

I understand that it won't automagically appear in Reason :) Just trying to understand the roadmap regarding this feature. Probably it's of low priority, as BuckleScript does not support that,...

While it all works, and we can live with this, resulting code after formatting is very counter-intuitive especially with meta-quoting semantics when you want a clean separation between what's inside,...