LeeTibbert
LeeTibbert
Arman, thank you for reading this Issue. Overall: My motivating goal is to be able to write, at the end of the trail, `stackalloc[Byte](5)` without a lot of eyesore faffing...
##### Later: From lots of attempts to capture it, I believe the annoyance I am seeing about stackalloc[Byte](5) requiring a (5.toUSize) occurs only in the Scala Native build environment itself....
Scala Native has access to `inet_pton`, `inet_ntop`, and `getaddrinfo`. The provisional fix is to remove the now 12+ years old Java inspired InetAddress conversion routines and use the system standard...
Me too! Me too! TLDR; Replicated in lots of configurations. Replicated using "tests3/testOnly *ProcessTest" // make ProcessTest earn its keep. macOS 12.5, Apple M1 ``` Apple clang version 13.1.6 (clang-1316.0.21.2.5)...
If I understand this new information correctly, brew clang works, but Apple(xcode?) and LLVM do not. At least now there is a known workaround. When I have nothing to do,...
Must be better karma, more skill, or better versions, in Europe...
Spent an evening chasing this. No joy. First I made sure that I had the correct brew clang version. I had to edit my PATH as described in the brew...
I hope to chase more this weekend. The url referenced at the end indicates that this might be fixed soon, llvm 15, llvm 16? A SN fix might need additional...
The version of xcodetools might be making a difference here. Apple put some linker changes into xcode 13 and LLVM has not caught up to those yet. I think I...
1) The title should probably change to "Apple" I think this is a problem with both Intel & M1. 2) A measure of success. Falling back to brew llvm@11 makes...