Eric K Richardson
Eric K Richardson
I already edited in the first comment.
Note: some `java.security` classes are used in Java jar/zip code.
Since we are essentially using Early Semantic versioning, we should be able to remove or change behaviors between 0.4.x and 0.5.0. I think these can be removed for 0.5.0 since...
I think the most important thing if we remove deprecated code is that we somehow make sure we capture them with workarounds for the release notes. Maybe we should add...
You can copy `0.4.0.md` since that was the last breaking version to `0.5.0.md` and start filling that out with details of the removals. That would give us a head start....
My thought was that when using POSIX, one would include the the C lib as follows: ```scala import scalanative.libc.stddef._ import scalanative.posix.stddef._ ``` This gives you the Std C definitions along...
I think that anyone wanting to use POSIX which is a low level C API on Scala Native can easily add 2 imports. Unless you use conditional linking it won't...
Interesting I deprecated the following in `clib` but it is also in `posixlib` probably linking with the C file included in the `clib`. ```scala @name("scalanative_sigusr1") def SIGUSR1: CInt = extern...
Thanks for you contribution. We will have to work with you a little to get everything just right and some things may not be written in the Developer's guide so...
I don't think you can do anything but install clang-format v6 and use that.