This is the patch from the PR that has been closed right? I don't think it's a problem with the language itself, there are several production quality tools out there using libpcap.
There are some requirements that must be met regardless of how much safety the language provides:
1. Fuzzing on the packet parsers
2. Extensive unit testing
3. Separating privileges in a good way. This can be easily done the way other tools based on pcap are doing
The PR was closed for two reasons: privacy concerns (which may be negotiable with a blueprint issue), and the lack of the above 3 requirements (mandatory, biggest issue)