RFC: Drop the "--unhandled-rejection" CLI flag and exit on unhandled rejections

[saghul]

Every other runtime does that by default. Node allows customizing the behavior but I guess that's for historical reasons, we could add the equivalent option too.

[saghul]

PR: #791

[ChALkeR]

This is a bit problematic with #39
i.e. Promise.reject().catch(() => {}) being considered an unhandled rejection

It doesn't track unhandled rejections, it tracks any rejections and exits on them

I.e. this never prints and instead exits:

Promise.reject().catch(() => {})
Promise.resolve().then(() => console.log('ok'))

[saghul]

Do you have any suggestions?

[ChALkeR]

I would argue that not crashing the process on handled rejections is more important that reporting unhandled rejections.

Every other runtime does that by default.

Those don't crash the process on handled rejections, so the rationale behind this change doesn't hold?

So perhaps this should be reverted until #39 is fixed.

---

Side note: also jsc CLI doesn't have unhandled rejection tracking enabled, but that is not very relevant

Enabling unhandled rejection tracking by default seems perfectly reasonable, but only under the assumption that it works (and does not misfire for all rejections, including handled)

[ChALkeR]

Specific suggestion: revert, reopen, block on #39.

[saghul]

I'll go through the entire discussion again because I remember there was something tricky about it.

[saghul]

I think I got it fixed: #1038