With 4.06 out, it's reasonable to have this as a default flag.
This would only change the behaviour for OCaml < 4.06, is that correct?
Yes, and for 4.06.x+default-unsafe-string. For this case I would consider checking for the value of default_safe_string via ocamlc -config first.
Changing the default is likely to break a lot of stuff
So will dune 1.0 :)
With dune, ocaml support will be a plugin (a builtin one, #461 ). So I guess for such changes, we'll simply bump the plugin version.
People could still add unsafe-string to their list of flags, but I'd argue that a package that is not safe-string compliant in 2018 is somewhat broken anyway 馃槒
Yh, I agree that it should become the default, but we can't change it silently or it will break a lot of released packages in opam. It seems fine to change the default during the migration to Dune though
Most helpful comment
Yh, I agree that it should become the default, but we can't change it silently or it will break a lot of released packages in opam. It seems fine to change the default during the migration to Dune though