0005777: Update mode for inferring mli files

Notes
(0008369) Bardou (reporter) 2012-10-30 14:42	What about the following example: type t = int let f x = x + 1 interface: type t val f: t -> int I now change implementation as follows: type t = float let f x = x +. 1. The inferred type for f is float -> float. How should the .mli be updated? I would like: val f: t -> float But it does not seem easy to decide that we want to keep t.

(0008371) frisch (developer) 2012-10-30 16:37	I really don't like the idea that the compiler would parse some source file, modify it, and save it back. I've nothing against an external tool trying to do it properly (preserving the formatting and comments of the original file), but I don't think this is robust enough for a compiler and that we should encourage this workflow.

(0008375) hongboz (developer) 2012-10-31 02:42	frisch, I agree with you, how about my proposal?

(0008379) frisch (developer) 2012-10-31 17:24	> how about my proposal? Do you mean the "private" syntax proposed in 0005764? I don't have a strong opinion on the subject. For me, having to write the .mli file is not a problem. But it makes sense to have a way to define a structure item for the rest of the module but hide it automatically from the resulting signature.

Relationships