Bizzare type signatures in utop about base HOT 9 CLOSED

I get these type signatures in merlin output too, I don't think it's a utop issue.

from base.

from base.

I do not see this issue with base. I could reproduce this issue with core_kernel and core.
@lpw25, will this be solved with the new short path.

from base.

It should be, although partly by luck. Really ppx_sexp_conv should move to using attributes instead of special type names, then we could remove the sexp_list type from the environment.

from base.

ppx_sexp_conv already seems to support a generalisation of sexp_{list,bool,array,option}, see defaults. The next step is to remove the 'a sexp_list = 'a list alias from Base and replace the uses of the special type names with the new attributes.

Merlin also shows sexp_{list,bool,array,option} instead of {list,bool,array,option}, for example when running MerlinTypeOf on Base.List.

from base.

any workarounds?

from base.

We're working on changing ppx_sexp_conv so that these type definitions become unnecessary. That should fix the problem.

from base.

See f7770ef.

from base.

This issue is old enough that it's likely stale. And indeed I checked some of the examples cited above and indeed the special sexp_ types are no longer being used, and the type alias for the hash table constructor has been expanded.

from base.