CyclicReference

Convert to message. This takes an additional Context, so that we use the context when the message is first produced, i.e. when the TypeError is handled. This makes a difference for CyclicErrors since we need to know the context where the completed symbol is referenced, but the creation context of the CyclicReference is the completion context for the symbol. See i2887b for a test case, where we want to see "recursive or overloaded method needs result type".

Will the stack trace of this exception be filled in? This is expensive and only useful for debugging purposes.

Uses creationContext to produce the message

Returns a string representation of the object.

The default representation is platform dependent.