Business
Jobs
  • About Us
  • Solutions
    • Job Postings
      Post your job and receive qualified candidates in 48h.
    • Candidate Assessments
      500+ technical and psychological tests, plus anti-fraud.
    • Headhunting
      Tailor-made executive search from start to finish.
    • Payroll + EOR
      Payroll dispersal and EOR across 15+ LATAM countries.
  • Pricing
  • Jobs

0

509
Views
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 answers
Answer question

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 Report

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 Report

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 Report
Answer question
Find remote jobs

Discover the new way to find a job!

Top jobs
Top job categories
Business
Post vacancy Pricing Sales
Legal
Terms and conditions Privacy policy
© 2026 PeakU Inc. All Rights Reserved.
Andres GPT
Show me some job opportunities
There's an error!