Feature to prevent throwback of type definitions #282
Labels
Kind/Feature-request
New feature or request
Milestone
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Right now, in Real World OCaml, every type definition is thrown back to the user, which is no what you want typically, since the type definition itself contains essentially the same information. It would be useful to have some flags to control this behavior, both on a block-by-block basis, and flags to set defaults at the tool invocation level, so we can set broad defaults.
I can think of three modes that would make sense to switch between.
In all of the above, type errors should still come through. Note that in the case of type definitions with deriving clauses, like this one:
that one should expect the following in suppress-types mode:
i.e., the derived value declarations should come through, but not the types.
I propose that module declarations make it through in suppress-types mode, even if those modules contain only types.
Note that something close to the "suppress all" behavior is available by dropping the # syntax. But it would be good to have this control while still keeping the basic syntax. Indeed, in suppress types mode, it would be useful to have some lines that are type definitions and some that are value declarations in the same block, and have their behavior vary as suggested above.
The text was updated successfully, but these errors were encountered: