fix js exit behaviour

[TanklesXL]

This change is a preliminary bugfix in order to addess #55

[TanklesXL]

@ghivert does this behaviour properly un-break glint in the browser?

[ghivert]

Isn't it dangerous to just do this? Because the process will continue to execute. Are you sure it will stop all other operations? 🙂

(By the way, I did not know GitHub allows to review PR like that, even if you're not on the repo. Weird experience. I just clicked on "leave single comment", so do not take it as me trying to review properly. 😅)

[TanklesXL]

Isn't it dangerous to just do this? Because the process will continue to execute. Are you sure it will stop all other operations? 🙂

(By the way, I did not know GitHub allows to review PR like that, even if you're not on the repo. Weird experience. I just clicked on "leave single comment", so do not take it as me trying to review properly. 😅)

That's a good point, this won't stop the current process from executing, this is effectively the same as running glint with glint.without_exit. (maybe it's worth just setting that if in the browser and documenting that explicitly?)

As a workaround right now, there is the exported but undocumented alternative to glint.run that is glint.execute that is

@internal
pub fn execute(glint: Glint(a), args: List(String)) -> Result(Out(a), String)

i wonder if that is a decent option

[TanklesXL]

Thinking about this more, with it being an implicit glint.without_exit, glint will still behave and run normally it just wont kill execution, it just won't end the current process. I can't stop a developer from putting code after glint executes (nor do i think i'd want to)

[ghivert]

Do you want me to properly test the change? 🙂

[TanklesXL]

Thanks for the offer! after thinking about it a bit more, I'm planning some upcoming changes for glint v2 that will rip all IO out of the core so I think it may not be necessary