Shawn Yang

Looks good to me, using maven can avoid to setup sbt and learn how to use sbt. And the fury scala build is not complex, maven scala plugin is more...

@qinzhikui thanks for creating this issue, could you provide the reproduction code and fury version?

Seems this is a multi-thread related issue, but it's not easy to figure out what happend without the reproduction code. I checked the implementation, this exception should not happen.

I'll try to reproduce it, and give you feedbacks if I make it

> Can I try to do some work on this? @chaokunyang Of course. Welcome to try this issue. Thanks for the willingness to contribute to Fury.

I haven't try bazel on Windows. If you want to try this issue, you may need to install bazel on Windows first, and fix some compilation issues.

I see, thanks, I'll try it when I have time

We do support javascript on nodejs and chrome. @wangweipeng2 can share more details.

Maybe we can use `java.lang.invoke.MethodHandle` to load scala classes dynamically to avoid source dependency on scala library. In this way, we can avoid release different jar for different scala version...

> Supporting Serialization/Deserialization of Collection is very hard with Java Reflection only. The T is erased when the T is a primitive type. Scala has its own separate reflection libraries...