Exceptions are not a type but rather a globally accessible way to "crash" your sneq program. Similar to panic in other languages, raising an exception is the one exception to functional purity and gives all sneq functions an escape hatch.

In parts of the UI, the exception mechanism also provides a way for the user to interact with the user interface. For example, return Exception('Foo') in a reservation or request script will set the conflict string displayed to the user to "Foo".

They must be returned. They will break out of any nested function and cause the value in Exception to be returned.

def foo():
  return Exception('No one may reserve this.')
return foo()