[Feature] [Xlang] Auto method name translation

Search before asking

• I had searched in the issues and found no similar feature requirement.

Description

A common issue when communicating between Java and Python using the cross language API is the method name convention is not consistent for the language.

For example when calling java from Python

counter_class = ray.java_actor_class(
      "io.ray.demo.Counter")
counter = counter_class.remote()
# Note the camelCase
counter.incrementValue.remote()

calling Python from Java is less worried because you have to create PyActorMethod by string. But the snake_case still stand out.

    PyActorClass actorClass = PyActorClass.of(
        "ray_demo", "Counter");
    PyActorHandle actor = Ray.actor(actorClass).remote();
    ObjectRef objRef1 = actor.task(
        PyActorMethod.of("increment_value", int.class)).remote();

The mix of camelCase and snake_case is harms readability and compatibility. For example, in Ray Serve, our Python actor needs to manage both Java and Python actors, we have to sprinkle these cases everywhere:

if lang = "JAVA":
    ref = actor.performTask.remote(...)
else:
    ref = actor.perform_task.remote(...)

Proposal

Ideally, I can just call a snake_case method on Java actor handle and have it automatically translated to camelCase method name. so that

    ref = java_actor.perform_task.remote(...)

automatically resolves to the actor’s performTask method.

[jon-chuang]

I feel that this should be opt-in. So

counter_class = ray.java_actor_class(..).set_snake_case_methods()

[jovany-wang]

It’s natural for Java and Py. But I’m not sure if it’s a good idea for other languages. For example, C++ has no strong recommend on the function name style. @qicosmos CC

I think it won’t be a problem if we let users specify the desired naming conversion explicitly, like what @jon-chuang recommended above.

Yes. Proposal from @jon-chuang looks good.