Go release.2010-10-13 removed "exp/iterable", so it is questionable whether containment matches should still support channels. But for now the channel support has been left in place. The matchers' toArray function now requires explicit support for each container type (it violates the Open-Closed Principle).
The same fix as before was needed also in another place. Now the fix has been moved inside the method which needs it, so this bug should not anymore reappear.
See the comments at http://code.google.com/p/go/issues/detail?id=1100 for an explanation of the cause
Although the GoSpec would compile and run also on Go release.2010-08-25, the line numbers of asserts would be incorrect (due to the refactoring in the previous commit), so it's better to say that anything below Go release.2010-09-06 is not supported.
…k traces are now correct
…cing a Message type
gedit has some trouble in making the file paths clickable in its shell output window, if the same line contains any non-ASCII characters. Since in Go methods have the interpunct "·" in their internal name, this is very common. As a workaround, let's put a newline between the function name and file path in stack traces.