A modern programming language that makes developers happier.

kotlinlang

<https://blog.shreyaspatil.dev/kotlin-exception-handling-why-singleton-exceptions-are-a-bad-idea|https://blog.shreyaspatil.dev/kotlin-exception-handling-why-singleton-exceptions-are-a-bad-idea>

exceptions can be created without a stack trace, which would also prevent them from being misleading

I once ran into this, too. :smile:

What use do Exceptions without a stack trace have?

I feel Detekt should have a rule for singleton/`object` Exceptions.

control flow exceptions that aren't exposed to the user

Ok, I see. Control flow exceptions are considered being an anti-pattern in my world. :wink:

( No, I don't have an alternative for CancellationException :sweat_smile: )

<@U025FAKGGJY> Detekt has the rule :nerd_face:

<https://detekt.dev/docs/rules/exceptions/#objectextendsthrowable>

&gt; Control flow exceptions are considered being an anti-pattern in my world.
Actually it's the opposite way around :sweat_smile:  Control flow exceptions are bad _because_ their stacktrace is expensive

If you disable stacktraces, and carefully write a DSL so the exception cannot "leak", you can use them fairly safely as a sort of more powerful non-local return

The best example I know is <https://arrow-kt.io/learn/typed-errors/working-with-typed-errors/>