Hello, Justus Winter, on Sat 04 Jun 2016 15:45:15 +0200, wrote: > tl;dr: Compiler-assisted runtime checking of port handling in > variables with automatic storage duration. Do we want to go there?
That's interesting, but the proposed way would need annotating the whole source code, I'm afraid we'll make mistakes there. Passing a port to a function that will deallocate it will probably need another macro BTW. Ideally we'd have a static analysis tool which knows about the mig rules for port references. Perhaps LeakSanitizer could be taught that? (we probably want to port it to Hurd, anyway, and it seems very portable) Samuel
