I've hit this problems a few times, and I immediately thumbs-upped that
issue report.
To correct @Ben, I suggest the purest reasoning for an error being
displayed is "The process completed, and did not succeed". In your case,
@Ben, yeah, it was killed while waiting on something, but the normal
> Depending on implementation, infinite recursion is not guaranteed to blow
> the stack for the program given. The function call is in tail position, so
> a tail-call optimization (TCO) pass would be able to rewrite the program
> into an infinite loop by reusing the existing stack frame for ea
On Wed, Apr 6, 2022 at 3:18 AM ben...@gmail.com wrote:
> Normally the Go Playground gives errors when a runtime panic or other
> error occurs, including "timeout running program" for programs that run too
> long. I'm wondering why the Playground doesn't show a stack overflow error
> (or any error
Oh wait, looks like it's public: https://github.com/golang/playground
On Wednesday, April 6, 2022 at 3:32:11 PM UTC+12 ben...@gmail.com wrote:
> Sure, report an issue against the playground. I honestly have no idea
>> how difficult this would be to fix.
>>
>
> Thanks, done: https://github.com/g
> Sure, report an issue against the playground. I honestly have no idea
> how difficult this would be to fix.
>
Thanks, done: https://github.com/golang/go/issues/52176
The source for the Playground is private, correct?
-Ben
--
You received this message because you are subscribed to the Goo
On Tue, Apr 5, 2022 at 6:50 PM ben...@gmail.com wrote:
>
>> The playground isn't intended to be an exact replica of running a
>> program on a real machine. If the program uses too many resources it
>> will simply be stopped.
>
>
> Both fair enough. But surely the runner can distinguish when the pr
On Tue, Apr 5, 2022 at 6:18 PM ben...@gmail.com wrote:
> Normally the Go Playground gives errors when a runtime panic or other
> error occurs, including "timeout running program" for programs that run too
> long. I'm wondering why the Playground doesn't show a stack overflow error
> (or any error
> The playground isn't intended to be an exact replica of running a
> program on a real machine. If the program uses too many resources it
> will simply be stopped.
>
Both fair enough. But surely the runner can distinguish when the program
ran successfully to completion versus when it was st
On Tue, Apr 5, 2022 at 6:18 PM ben...@gmail.com wrote:
>
> Normally the Go Playground gives errors when a runtime panic or other error
> occurs, including "timeout running program" for programs that run too long.
> I'm wondering why the Playground doesn't show a stack overflow error (or any
> e
Normally the Go Playground gives errors when a runtime panic or other error
occurs, including "timeout running program" for programs that run too long.
I'm wondering why the Playground doesn't show a stack overflow error (or
any error) for this infinitely-recursing program?
https://go.dev/play/
10 matches
Mail list logo
