Errors

Note

All Chapel programs automatically use this module by default. An explicit use statement is not necessary.

Support for error conditions and error-handling.

This module contains several features related to error conditions and error handling:

class Error

Error is the base class for errors

proc init()

Construct an Error

proc init(msg: string)

Construct an Error with a message.

proc message(): string

Override this method to provide an error message of type string in case the error is printed out or never caught.

Return type

string

class NilThrownError: Error

If a nil Error is thrown, NilThrownError will be thrown instead.

class NilClassError: Error

A NilClassError is thrown if a cast from a nil class is made.

class ClassCastError: Error

A ClassCastError is thrown if a cast between class types fails and the destination is not nilable.

class DecodeError: Error

A DecodeError is thrown if an attempt to create a string with non-UTF8 byte sequences is made at runtime. This includes calling the bytes.decode(decodePolicy.strict) method on a bytes with non-UTF8 byte sequences.

class IllegalArgumentError: Error

An IllegalArgumentError is thrown if bad arguments are passed as arguments to procedures.

proc init(info: string)

Warning

new IllegalArgumentError(info=) is deprecated; please use the initializer that takes a formal msg instead.

proc init(formal: string, info: string)

Warning

IllegalArgumentError’s two-argument initializer is deprecated; please use the single-arg initializer instead.

class CodepointSplitError: Error

A CodepointSplitError is thrown when slicing a string with byteIndex-based ranges where the range boundaries do not align with codepoint boundaries.

class ArrayOomError: Error

Warning

ArrayOomError is unstable; expect this error to change in the future.

type CodepointSplittingError = CodepointSplitError

Warning

CodepointSplittingError is deprecated; please use CodepointSplitError instead

class TaskErrors: Error

TaskErrors stores multiple errors when they can come up. For example, a coforall loop might throw errors from multiple tasks at the same time. These errors will be reported to the parent task at the end of the coforall in the form of TaskErrors.

Note that errors thrown within a coforall, cobegin, or forall are represented as elements of TaskErrors. In the case of nesting, all errors will be stored in a single TaskErrors.

Errors thrown in begin tasks will be reported within a TaskErrors to the task that uses sync to wait for those begin tasks.

proc init(err: unmanaged Error)

Create a TaskErrors containing only the passed error

proc init()

Create a TaskErrors not containing any errors

iter these() ref: owned Error?

Iterate over the errors contained in this TaskErrors. For example

var taskErrors:TaskErrors = ...;
for containedError in taskErrors {
  // Do something with the contained error
}

Yields references to owned Error? so that one of the yielded errors might be re-thrown. Only yields values that are not storing nil at the time of the call.

proc first() ref: owned Error?

Warning

TaskErrors.first is unstable; expect this method to change in the future.

Returns the first non-nil error contained in this TaskErrors group

override proc message(): string

Returns a string summarizing the errors contained in this TaskErrors. The summary is intended to be concise: it will not grow arbitrarily long if the TaskErrors contains many errors.

iter filter(type t) ref: owned Error?  where isSubtype(t: borrowed class, borrowed Error)

Iterate over those errors contained that are the passed type or a subclass of that type.

Note that this iterator yields values of type owned Error? but only those that are non-nil and have dynamic type t.

proc contains(type t)

Returns true if this TaskErrors contains an error of the given type or a subclass of that type.

proc assert(test: bool)

Assert that a boolean condition is true. If it is false, prints ‘assert failed’ and halts the program.

Note

In the current implementation, this assert never becomes a no-op. That is, using it will always incur execution-time checks.

Arguments

test : bool – the boolean condition

proc assert(test: bool, args ...)

Assert that a boolean condition is true. If it is false, prints ‘assert failed - ‘ followed by all subsequent arguments, as though printed using write().

Note

In the current implementation, this assert never becomes a no-op. That is, using it will always incur execution-time checks.

Arguments

  • test : bool – the boolean condition

  • args – other arguments to print

proc compilerError(param msg: string ...)

Generate a compile-time error. The error text is a concatenation of the arguments.

proc compilerWarning(param msg: string ...)

Generate a compile-time warning. The warning text is a concatenation of the arguments.

proc compilerAssert(param test: bool)

Generate a compile-time error if the test argument is false.

proc compilerAssert(param test: bool, param msg: string ...)

Generate a compile-time error if the test argument is false. The warning text is a concatenation of the string arguments.

proc exit(status: int = 0)

Exit the program.

The compiler ignores the code following a call to exit until the end of the block where this call is made.

Arguments

status – The exit code for the program

proc halt()

Prints an error message to stderr giving the location of the call to halt in the Chapel source, then exits the program.

The compiler ignores the code following a call to halt until the end of the block where this call is made.

proc halt(args ...)

Prints an error message to stderr giving the location of the call to halt in the Chapel source, followed by the arguments to the call, then exits the program.

The compiler ignores the code following a call to halt until the end of the block where this call is made.

proc warning(msg: string)

Prints a warning to stderr giving the location of the call to warning in the Chapel source, followed by the argument(s) to the call.

proc warning(args ...)

Prints a warning to stderr giving the location of the call to warning in the Chapel source, followed by the argument(s) to the call.