Missing Exit.getOrUndefined, et al.

[jessekelly881]

What is the problem this feature would solve?

The Exit module is missing getOrUndefined, getOrNull, etc. These should probably be updated to match the Either module.

What is the feature you are proposing to solve the problem?

^

What alternatives have you considered?

No response

[datner]

Should we really promote skipping handling an Exit like that when the alternative is to opt-into an Option / Either instead of an exit to begin with? 🤔

[jessekelly881]

We probably shouldn't promote it but the api should probably be consistent with Either. I have a bit of an edge case where I have to run Effect.runExit() and then return undefined if the effect fails.

[datner]

whats runExit?
@jessekelly881 I think this would cover your case fine tbh

const val = Effect.runSync(Effect.option(effect))
// const val = await Effect.runPromise(Effect.option(effect))
return Option.getOrUnderfined(val)

[jessekelly881]

Effect.runPromiseExit sorry. There are plenty of ways to achieve the same result. I just think that Exit should probably have a similarly complete set of getX fns as Either.