lance

lance copied to clipboard

I propose to create a directory for Java/Scala interfaces, which includes:

• Rust code for make JNI compatible interfaces.
• Java code for JNI interfaces.
• Java code for minimal interfaces that let Java/Kotlin/Groovy users can work with, and we create Scala interface based on them.
• Scala code for expressive interfaces that let Spark users can work with.

How about name the directory with jvm?

I vote just call it /scala . Calling it /jvm is strictly less information and no more correct. It means "this is the Scala wrapper" and not "this directory only contains Scala code" - otherwise you wouldn't even be allowed to put txt or markdown files since they're not "JVM".

call it /scala is fine for me, for me it implies the directory is optimized for scala users though it's also workable for other jvm users.

Should a java sdk be the core so that it will be later used by scala / kotlin or sth else?

Should a java sdk be the core so that it will be later used by scala / kotlin or sth else?

I think so, that's one reason I want name it by jvm, create two directories java,scala is not convenient since we may still want them managed by the same build tool(so far I want sbt be the tool).

Closing due to inactivity. Let's revisit once we have some more details on how to do the JVM integration better.