3. RawMemory.foreignSegment should be more consistent

RawMemory.foreignSegment should be more consistent


  • Currently if you call setActiveForeignSegment and there's nothing there your RawMemory.foreignSegment will be entirely undefined. But if there's a public segment there you get the username, id, and data of the segment in an object. I'd like to request that if you have a foreign segment assigned and there isn't one there, that we return the same object format. username, id, and data would be null or undefined.