You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Tracking down Uncaught RangeError: Maximum call stack size exceeded errors has been the number one pain in a otherwise very enjoyable GopherJS experience. Once I managed to get the complete stacktraces from the browser, the causes are obvious.
But the example above isn't obvious to me.
I can understand why a circular referenced object should fail (however, you should consider document it as a difference between the Go stdlib), but the abvove I would expect to plainly return false. But there may be stuff here I don't see.
The text was updated successfully, but these errors were encountered:
Uh oh!
There was an error while loading. Please reload this page.
See http://www.gopherjs.org/playground/#/54CnvrqcGt
Tracking down
Uncaught RangeError: Maximum call stack size exceeded
errors has been the number one pain in a otherwise very enjoyable GopherJS experience. Once I managed to get the complete stacktraces from the browser, the causes are obvious.But the example above isn't obvious to me.
I can understand why a circular referenced object should fail (however, you should consider document it as a difference between the Go stdlib), but the abvove I would expect to plainly return
false
. But there may be stuff here I don't see.The text was updated successfully, but these errors were encountered: