Douglas Hall

jwpowell is right, libraries should never have side-effects like logging or printing unless otherwise instructed. Especially if there's no way to disable or filter it.

According to http://godoc.org/runtime#SetFinalizer a finalizer should not be used for freeing memory since it's not guaranteed that a finalizer will be run before the program exits.

It's still a memory leak if the finalizer isn't guaranteed to be called. The GC won't touch data that isn't allocated by Go, it has to be freed somewhere.

In my testing Go's memory alignment isn't much of an issue for performance. Although I haven't been able to test on any other architectures or OS's other than windows and...

Although, plans must still be destroyed even if you provided your own input and output arrays.

It's pretty likely your meter is already transmitting ERT-flavored messages, it may just be a matter of finding the right message type, and frequency the meter is transmitting on. I'd...

From your captures, can you tell me what the modulation is?

Hmm, can you provide some sample captures?

I mean IQ data, if possible.

See #284