javalibis not splited into
javalibas it's in scala-js
java.*namespace (i.e., nothing from the Scala lib or the Scala.js lib). Eventually I'd like to get that check to apply to javalib as well, but we're not there yet.
Ok, rebased corectly to last master. I also made trivial changes: scala-native/scala-native#1971
Convert unsafe.CStringSuite.scala to JUnit unsafe.CStringTest.scala. Thank you, it saved me days.
re: The TreeMap is holding you back? The TreeMap work was in support of scala-java-time, particularly their ScalaTest code. I believe that @catap found a way to get those working without TreeMap. TreeMap was used in the sjt Java code. The sjs platform used other code, marked as inefficient. So, my javalib TreeMap work fell to the back of the pack. Not forgotten, not deleted, but distant. I know of no javalib TreeMap in public Scala.js or Scala Native repositories. SN does have the Scala TreeMap, but that has different methods, etc.
Short story, thank you for checking but you are not blocking me.
able to accomplish the scala-java-time tests without having to implement TreeMap.scala. Good for you!
On my first reconnaissance run at sjt testing, I copied over the sjt code for scala.js, but that code had warnings in it about its
inefficiency. I believe that the sjt JVM branch used TreeMap.scala. So, I took a run at implementing TreeMap.scala,
with the idea of ScalaNative then Scala.js. Dreams! I got pretty far before I fell into my current pit of recursive interruptions. I see why scala-java-time js went with a partial simple implementation, suitable to need.
So all of this is to say that TreeMap.scala does not, to the best of my knowledge, exist yet. (Add to say "Well done!" )