Error type
Represents an error. Usually more specific error types are used.Direct parent types
- Exception
- Represents exceptional situaution. All thrown things shouhld inherit Exception.
Direct subtypes: 10
Direct children types
- BoxFail
- Thrown when trying to get() a value from EmptyBox and no default value given.
- CallFail
- Represents calling failure.
Direct subtypes: 4
- CError
- Base type for exceptions arising from errors returned by calling C functions
Direct subtypes: 9
- CompileFail
- Represents a compilation error.
- DecodeFail
- Represents an error decoding a data.
Direct subtypes: 1
- DlopenFail
- Represents failure to open dynamically loaded library (feature is a work in progress).
- ExitCodeFail
- Represents error when converting program execution result to exit code
- InstantiatingAbstractType
- Represents an attempt to create an instance of an abstract type (not intended for instantiation).
- InternalError
- Represents an error which is likely to be NGS implementation bug.
- InvalidArgument
- Represents an error of calling a method with incorrect argument.
Direct subtypes: 5
- LookupFail
- Represents an error of accessing non-existent element of a collection.
Direct subtypes: 5
- MainFail
- NotImplemented
- ReadFail
- RegExpCompileFail
- Represents a regulat expression compilation error.
- RequireFail
- ResultFail
- Thrown by get(Failure) as it has no value to get
- ResultsException
Direct subtypes: 1
- RetryFail
- Represents failure on all retries
- SkipError
- StackOverflow
- Represents a stack overflow error.
- SwitchFail
- Represents missing appropriate eswitch/econd/ematch clause.
- TestFail
- TrFail
- Represents failed transformation
Direct subtypes: 1