Empresas
Empleos
  • Sobre nosotros
  • Soluciones
    • Publicación de vacantes
      Publica tu vacante y recibe candidatos calificados en 48h.
    • Evaluación de candidatos
      500+ pruebas técnicas y psicológicas, más anti-fraude.
    • Headhunting
      Búsqueda ejecutiva a la medida de principio a fin.
    • Nómina + EOR
      Dispersión de nómina y EOR en más de 15 países de LATAM.
  • Precios
  • Empleos

0

511
Vistas
What's the equivalent of Swift's fatalError() in Kotlin

Say I want to do sth like

val foo = when(bar) {
   "one" -> true
   "two" -> false
   else -> // in Swift it would be `fatalError()`
}

How do I do it?

I'm aware that there are generally better approaches to this kind of problem, but I want to know how to easily induce a crash in Kotlin too :)

over 4 years ago · Santiago Trujillo
3 Respuestas
Responde la pregunta

0

You could throw an exception. This will bubble up the call stack until somebody handles it or you run out of stack frames and the application crashes.

val foo = when(bar) {
   "one" -> true
   "two" -> false
   else -> throw IllegalArgumentException("$bar is Unknown")
}

I just used IllegalArgumentException here, but you might want to define your own.

over 4 years ago · Santiago Trujillo Denunciar

0

If you look at the TODO() global function in Kotlin:

public inline fun TODO(): Nothing = throw NotImplementedError()

You can see that it is a function that returns Nothing (similar to Swift'sNever), and it throws a NotImplementedError.

With this, we can create our own fatalError function to mimic Swift:

public fun fatalError(message: String = ""): Nothing = throw NotImplementedError(message)

And because it returns Nothing you can use it the same way you would in Swift:

fun getValue(): Boolean = when(this) {
  "true" -> true
  "false" -> false
  else -> fatalError("Cannot determine value for $this")
}
over 4 years ago · Santiago Trujillo Denunciar

0

Throwing an exception (or, better still, an Error) is one way, but it may not shut down the current thread: any of the calling functions could catch the exception, or an UncaughtExceptionHandler could have been set for the Thread (or its ThreadGroup).

Nor will it shut down any other threads that may be running.  (Even if you haven't started any yourself, they're used by coroutines, GUI toolkits, and other execution frameworks.)

To shut down the whole app, you should use the Kotlin exitProcess() function, or in Kotlin/JVM the equivalent System.exit() method.  That will terminate all threads.

But even that will do a ‘graceful’ shutdown, running any shutdown hooks, finalizers, &c.  If you need to forcibly kill a Kotlin/JVM app immediately, call Runtime.getRuntime().halt().

(And of course, it's probably good practice to first display something to stdout or the logging framework you're using, to indicate what the problem was.)

over 4 years ago · Santiago Trujillo Denunciar
Responde la pregunta
Encuentra empleos remotos

¡Descubre la nueva forma de encontrar empleo!

Top de empleos
Top categorías de empleo
Empresas
Publicar vacante Precios Comercial
Legal
Términos y condiciones Política de privacidad
© 2026 PeakU Inc. All Rights Reserved.
Andres GPT
Recomiéndame algunas ofertas
Necesito ayuda