Hypothetically speaking, is there anything stopping an eCore reading or writing to/from the local memory of an eCore in a different workgroup?
I know it's bad practice and I'm aware that the eSDK is not set up in this way (in that, the majority of functions deal with eCores within the caller core's workgroup) but if you could calculate the local memory address space of an eCore in one particular workgroup, could you read or write to that eCore from an eCore in another, separate, workgroup?
My hunch is that you can but I just wanted to double check.