JP Sugarbroad
JP Sugarbroad
I'm not clear on why `stack.switch` injects an exception into the receiving stack instead of just resuming it. Is it so that the `stackref` doesn't have to be typed?
I also don't understand the semantic difference between the `rout` that has a `stack.start` and a similar function that also accepts a `stackref` parameter.
Hm, well, the example you have catches two different exceptions at that point, so I retract my earlier comment. It is different from the equivalent function.
I'm in favor of degree 1. Feel free to add reacts to this message if you just want to agree.
Oh, I guess I didn't realize it showed under both. I'd like it to show under only one, or at least not show in the category bundle if it's in...
Mostly for compatibility with legacy workflows. It's been so long I've set up things to take advantage of the inbox types that gmail already has. Especially "Forums" label, which is...
No, I turned off priority inbox to make the extension work. But inbox was great about ensuring that I saw anything marked Important by not bundling those messages.
How does one enable mangling of the output? Run the output of spack through swc again?
Also tried running with the various other optional flags (e.g. protocols) and they don't fix the problem.
Is there a way to specifically override maximum call depth?