>You can read about Ocaml's nominal record typing in the [ReasonML docs](https://reasonml.github.io/docs/en/record https://reasonml.github.io/docs/en/record) (i

>You can read about Ocaml's nominal record typing in the [ReasonML docs](https://reasonml.github.io/docs/en/record https://reasonml.github.io/docs/en/record) (it's more clear there IMO). You are confusing records with structures, it seems. Structures exist in module language. Records are nominal in SML as well. Access functions for tuples and records are a dirty ugly hack build-in for convenience, they have nothing to do with structural typing, they are inferred in place. OCaml has structural typed records, they are called objects. let obj = object method pi = 3.14; method name = "Pi" end val obj : < pi : float ; name : string > is structurally typed record. > I can pass that record on to ANY function No, you can't. #foo { foo = 42 } works, but fun f x = #foo x doesn't. It's an ugly hack, typing is still nominal. A hack, just like SML's arithmetic op overload. Compare it to OCaml, which have proper structural typing for objects and raw polymorphism let f x = x#foo f : < foo : 'a; .. > -> 'a Edit: sorry, indeed typing is structural since you can write `{x:typ} -> typ`. Anyways OCaml have structural typed records and raw polymorphism and subtyping support for them. > Another nice property of the SML approach is that you don't need named arguments. Instead, pass a tuple with names (aka a record). What's your point? You can use records as arguments in OCaml as well.