You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Opening Core_kernel or Base bring the type aliases sexp_{list,bool,array,option} to {list,bool,array,option} into scope, which infamously infect OCaml tooling (merlin, utop) and confuse newcomers. See also janestreet/base#39.
ppx_sexp_conv already supports attributes that supersede the old type names. So we should encourage users to switch to attributes and fix the original problem by moving the type aliases out of Core_kernel and Base (maybe to a submodule?).
The text was updated successfully, but these errors were encountered:
Indeed, we have been talking about doing this change for a while. It's just that we never took the time to do it.
Regarding moving the types aliases to a sub-module, for the user this is basically as much work as switching to attributes. We could mark them deprecated with [@@deprecated] though.
It would be wonderful if 2019 could be the year in which we don't have to see sexp_list any more. The more one uses merlin, the more often they come up, which is quite unfortunate.
Opening Core_kernel or Base bring the type aliases
sexp_{list,bool,array,option}
to{list,bool,array,option}
into scope, which infamously infect OCaml tooling (merlin, utop) and confuse newcomers. See also janestreet/base#39.ppx_sexp_conv
already supports attributes that supersede the old type names. So we should encourage users to switch to attributes and fix the original problem by moving the type aliases out ofCore_kernel
andBase
(maybe to a submodule?).The text was updated successfully, but these errors were encountered: