Holger Dal Mogensen
Holger Dal Mogensen
Found it. If you're curious, it was reinitializing and spawning a new *REPL* on every reconnection.
> Did you try that this works in practice? E.g. if you start VSCode and enter sleep or hibernation then it works when you resume? It does, but I've only...
But sometimes the compiler process dies, e.g. if you (accidentally) kill it in task manager. Right now this will cause the compiler to be relaunched, otherwise VS Code would sit...
Resource leaks in what way? Again, it only relaunches it if it's already completely gone.
> > Resource leaks in what way? Again, it only relaunches it if it's already completely gone. > > You assume that because the port has been released the process...
Again, I really don't see that as a risk, and I think relaunching is the correct thing to do, but if that's what's blocking I'll remove the feature.
> Can you double check: > > * Everything still works after standby or hibernate? > > * Starting two VSCode instances works correctly? Yes, everything works on my machine....
I can fix it in the normal VS Code color scheme, but it's sort of a problem that the Flixify theme makes all keywords and operators the same color, so...
> I suppose I never thought about whether -> is a keyword or an operator. > > What if I want it to be neither? It just needs to be...
> What is `.` classified as(if anything)? It's not categorized as anything currently.