Names of anonymous classes cause issues

The names of anonymous functions are integers, and these are arbitrary. However, Spork treats them as if they have meaning for the anonymous function, which can cause content conflicts on anonymous functions even if there are none.

A quick fix for this is to simply not resolve the names of anonymous functions. The downside of that is that there could end up being multiple anonymous functions in the tree with the same name, and I'm uncertain of what effects that may have.

Start by locating Spork's anonymous-function name resolution and reproduce a content conflict involving anonymous functions with arbitrary integer names. Done means arbitrary names no longer create false conflicts, while the behavior when multiple anonymous functions share a name is understood and covered by an appropriate regression test.

Written by the indexing model from the issue text.