Unfortunately, we already have this burden, as the same type might have multiple names, e.g.,
'a option
'a Option.t
'a sexp_option
'a Base__option.t
etc
The same is true for value identifiers, thanks to module aliasing, e.g., Option.iter, Base__option.iter etc.
That’s not to say, of course, that we have to increase this burden, but to highlight that the problem was already there, even before the clash with the world of web developers with their CamelCase notation. And putting jokes aside, this problem should be addressed. Especially on the tooling level (doc generators, merlin, etc), which should follow the Internet Robustness principle and treat literals using their equivalence classes. This is how argot API search was implemented, and I believe, that @Drup was implementing at some point of time and space a better than Argot solution. Not sure if it was published somewhere.