I find it interesting that one of the reasons GO refuses to provide a way of identifying a routine's unique context is to prevent abusing that as a way of havin

I find it interesting that one of the reasons GO refuses to provide a way of identifying a routine's unique context is to prevent abusing that as a way of having a session key attached to it... and then the standard libraries go and make a ctx variable to do EXACTLY that. I think a solution would probably relate to looking at client connections.