out and leave the value on the
>> stack. My real code passes &opts to several functions without issue. The
>> only ones that cause a problem are the IndexFunc calls.
>>
>> For your index2 function question, I think it's because Go maintains the
>>> variable
If you have more time to spare on this project, try to circumvent the
events / subscriber functionality. Try to see if you can read directly from
the adaptor:
https://github.com/hybridgroup/gobot/blob/master/platforms/beaglebone/beaglebone_adaptor.go#L151
so inside your work function, you would d
