Unless I’m missing something, the in-memory backend here appears to actually use the set solution: all of the triple fields are concatenated together and used a

Unless I’m missing something, the in-memory backend here appears to actually use the set solution: all of the triple fields are concatenated together and used as a dictionary key. Queries iterate through the dictionary entries until a sufficient number of results have been located. On the other hand, I’m not really familiar with Go, so I may be reading it wrong.