LeeTibbert

Eric, thank you for your thoughts. I mostly concur. My overall thought is that `stackalloc()` clearing has been shipping for so many versions that Scala Native owns it as it...

fiatjaf thank you for this first contribution. I make a small re-organization recommendation in item 2 below. If implementing that change would be onerous to you, I can do a...

@fiatjaf I suggest/recommend re-opening this PR and letting it advance. It has value as both as 'the thing as it is' and as a first time contributor. You have done...

>The scala-native Javalib is not stuck at Java 8. > For example you can see in the test suite that there are tests for specifically JDK 11 and JDK 15...

> Due to the constraints of Scala Native 0.4.x being single-threaded we cannot implement everything > exactly as it's done in the JDK. Agreed, wholeheartedly. >If we can implement this...

fiatjaf, not to distract or dissuade you by differing opinions. As mentioned, I recommend you re-open this and let it flow through. That gives you a simple & successful walkthrough...

Arman, as collegial discussion. re: requirement for multithreading support I must be missing something about the expressed requirement for multithread support blocking implementing this from being in `InputStream`. I am...

iatjaf Thank you for re-opening and continuing the PR process. Putting concerns about `InputStream` on the stack for awhile, my only pending request is that you change the name of...

To summarize, I believe the consensus goal is to ship this PR and let motivated people do follow-ons? I think there are two tiny changes which are necessary. * The...

> Sorry for the delay. Thank you for the timely changes. This is the weekend, so that is fast turnaround in my book. I appreciate all the changes, but especially...