Apostrophe breaks function name derivation.

[pkel]

Consider the following signature:

module Date : sig get_day' : t -> int end

Using the function after deriving an implementation with gen_js_api results in an ugly runtime error. I suspect that the apostrophe finds a way into the javascript world.

[nojb]

What is the desired behaviour?

In general the name given in the interface is supposed to match the javascript name modulo casing and some other related conventions. Apostrophes are not valid inside identifiers in javascript, so probably it should not be used in the .mli to start with.

[alainfrisch]

It could make sense simply to drop those characters, thus allowing to bind multiple overloaded variants of JS functions.

[nojb]

Sure; but IIRC we can already do that today using underscores at the end of the identifier.

[pkel]

Overloading the function was my intended use case. After reading the documentation I expected gen_js_api to drop invalid characters. It says

When the naming is left implicit, a Javascript name is automatically derived from the OCaml name by applying the following rules: