Go 1.6 (to be released in February) has new rules about how Go and C can pass each other pointers. I suspect no changes will be needed in Pigosat, but I should at least make sure the tests do everything they need to ensure pointer safety when Pigosat is compiled under Go 1.6.
PS, for the other contributors/users of Pigosat: It will be a while before I can get to this (and the other pull requests). I started graduate school this fall, and that's left little time for hobbies.
Go 1.6 (to be released in February) has new rules about how Go and C can pass each other pointers. I suspect no changes will be needed in Pigosat, but I should at least make sure the tests do everything they need to ensure pointer safety when Pigosat is compiled under Go 1.6.
PS, for the other contributors/users of Pigosat: It will be a while before I can get to this (and the other pull requests). I started graduate school this fall, and that's left little time for hobbies.