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
Right now, I suspect Hopac just writes them in the standard error stream of the console, but I'd like to redirect it. I thought of doing my own TextWriter and setting it as the `Console.Error' in order to intercept them that way, but implementing it seems pretty difficult so I thought I should ask around first.
I am doing a language project that is currently in the alpha stage. It was fine to have a console window open while I was working on it alone, but now that Spiral is out on the VS Code marketplace the editor server will be running in the background. Since uncaught exceptions will always be compiler errors, I'd really like to report those as fatal errors in the editor. Besides Hopac which I am using internally for concurrency in the language implementation, at the outermost layer I am using NetMQ to communicate with the editor via TCP. This is why the standard error is not good for me.
The text was updated successfully, but these errors were encountered:
Right now, I suspect Hopac just writes them in the standard error stream of the console, but I'd like to redirect it. I thought of doing my own
TextWriter
and setting it as the `Console.Error' in order to intercept them that way, but implementing it seems pretty difficult so I thought I should ask around first.I am doing a language project that is currently in the alpha stage. It was fine to have a console window open while I was working on it alone, but now that Spiral is out on the VS Code marketplace the editor server will be running in the background. Since uncaught exceptions will always be compiler errors, I'd really like to report those as fatal errors in the editor. Besides Hopac which I am using internally for concurrency in the language implementation, at the outermost layer I am using NetMQ to communicate with the editor via TCP. This is why the standard error is not good for me.
The text was updated successfully, but these errors were encountered: