Nicolás Ojeda Bär

My understanding is that objects built with VS 2015 will work with newer versions, but not older.

In the short term, I think that shipping both versions would be best for "ease". But longer term, wouldn't it make sense to compile the support code as part of...

Rendered version: https://github.com/goldfirere/ocaml-rfcs/blob/unboxed-types/rfcs/unboxed-types.md

> > The main issue is that cmt files are huge and mostly useless. I think there are only two tools in the OCaml ecosystem that currently consume cmt files:...

Another con: `-ccopt` and `-cclib` will no longer work in general.

See the discussion at https://github.com/ocaml/ocaml/issues/9482

> Why not keep it to EXXX/WXXX, short and actually tells the user whether that's an error or a warning. This was also my first thought. Nice and simple. >...

I am not a 100% sure, but this may make the cut for 2.0.

> Ping. Would be indeed very nice to have a new release (especially with the `dune` port). Hello @samoht! Apologies for the long delay in getting back on this, I've...

Hi @shonfeder, and thanks for the offer! Sure, that would be a good first step. A bit of context: the project is basically "stalled" after a big rewrite because of...