Pitch #4: ConcurrentValue and @concurrent closures Evolution Pitches

[anandabits (Matthew Johnson)]

@Chris_Lattner3

we don't want functions to be equatable or hashable for implementation reasons. It isn't definable at the implementation level in a reasonable way.

I don't want to sidetrack this thread, but this has been discussed in the past. There is a reasonable case for function type equality defined by equatable captures and source identity of the function body. This is similar to how C++ uses anonymous types for each closure.