News for hackers. Stuff that matters.
Re:OCaml 4.03 will, “if all goes well”, support multicore by kuschku on Thursday May 21, 2015 @01:07PM (#9583983)
Or one could use the lisp-way – and just call the functions <record-name>-<field-name>.

This avoids those problems.

Re:OCaml 4.03 will, “if all goes well”, support multicore by gmfawcett on Thursday May 21, 2015 @01:30PM (#9584126)
The Ocaml way would be to define the functions in separate modules (A.foo, B.foo, etc.). There are convenient syntaxes for declaring which modules are in scope in a given expression, as well as support for first-class modules (you can define functions that take modules as parameters). The module system is sophisticated, and is arguably the "power feature" of Ocaml.
Re:OCaml 4.03 will, “if all goes well”, support multicore by creichert on Thursday May 21, 2015 @01:46PM (#9584240)
This is what you generally see in larger haskell programs which might have a name clash (at least it's what I use):

    data F = F { fName :: String }
    data P = P { pName :: String }
Re:OCaml 4.03 will, “if all goes well”, support multicore by LeonidasXIV on Thursday May 21, 2015 @05:52PM (#9585608)
Yes, this is one of the cases where ML modules are elegant, since you can put the definition of the type into its own module, so it becomes F.t and P.t and you avoid field name clashes.