Audit code, particularly the channel config for unsafe pointer assignments.

Golang pointers are word size, and therefore read/write operations across go routines are guaranteed to be consistent (ie, the previous, or the current value will be returned, not some mixture of the two).

However, there is still a risk due to out of order execution when a writer go routine writes a set of pointers, and a reader go routine reads that set of pointers, the reader go routine may not get what would be considered a consistent view of the system.

Although there have been no bug reports surrounding this sort of error, it is largely theoretical at the moment, an audit for these sorts of errors should be conducted, any instances of this potential fixed.