Right now, when we get a Segmentation Fault (SIGSEGV),
the REPL stops and returns to the shell.
This simply should not happen.
The REPL should handle this error.
Discussion
My first thought was to restart the REPL, that would not solve all the problem itself, but would help a lot, at least.
This would be the quickest approach, I suppose.
But, talking about long term, the right way would be to not suppress these errors, but instead, cover them, or properly handle them.
Other idea that cames in my mind is: when we get a Segmentation fault, the REPL handles or restart and then ask for the user to open an issue here.
So we can track and know about these errors.
Right now, when we get a Segmentation Fault (
SIGSEGV), the REPL stops and returns to the shell. This simply should not happen. The REPL should handle this error.Discussion
My first thought was to restart the REPL, that would not solve all the problem itself, but would help a lot, at least. This would be the quickest approach, I suppose.
But, talking about long term, the right way would be to not suppress these errors, but instead, cover them, or properly handle them.
Other idea that cames in my mind is: when we get a Segmentation fault, the REPL handles or restart and then ask for the user to open an issue here. So we can track and know about these errors.
Well, what do you think, @drkameleon?
Related
btiffin @ discord.com