JasonS05

A while back (a year ago maybe?) I could use go to compile or do anything else I might want to do with go and it worked fine but recently...

As I've mentioned before, already-compiled go programs work without issue (although now my mandelbrot program's output is buggy, but I think that's a terminal issue, not a go issue), but...

@alexandervlpl yeah it does seem rather unstable right now. Twice while messing around with trying to get go to work it just crashed in the middle of executing a command...

> I posted this to #dev on the discord as well. go does seem to work better on recent builds of iSH, but it still crashes after a small number...

I did some experimenting and I found that the issue isn't the random motion of the gas, but the collisions between the gas particles. Putting a cloud of gas in...

Thank you. I'll consider both options.

Seems this still isn't completely resolved. a46e77b causes a regression of its own. Specifically, the error message is lost since `msg` on line 79 of `/lib/process.lua` is not defined anywhere,...

Ok, I found another issue. My fix doesn't address what happens in an out of memory error. To properly report what happens, it appears better to fix it a different...

Here: ```Lua error("err") ``` Intended output: ``` /home/test.lua:1: err: stack traceback: ``` with exit code 128. Actual output (1.8.7): ``` : stack traceback: ``` with exit code 2. The other...

Ok, I don't know if this is related to this thread or not, but I found a possible error handling bug with some *really* cursed code. Here's the output: ...