-
Notifications
You must be signed in to change notification settings - Fork 89
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Error-handling as a struct, rather than just a string. (#13)
The `Error` struct can carry a lot of information into error messages for C++, but Numba can only raise serialized and globally registered exceptions. Therefore, the error messages from Numba have to be known at compile-time, which severely limits their specificity. Users with unhelpful error messages will have to re-run their code outside of Numba. * Foot-in-the-door to start implementing error-handling as a struct with feedback about the index position of the error (and therefore the Identity, too, if that's available). * Try to initiate a build from the new repository owner (scikit-hep). * Make sure I can still trigger builds. * Add classname() as a virtual method on all Content classes * Changed Error from a 'const char*' to a struct. * The 'failure' function didn't return an error (thanks, Windows compiler). * Start methodically testing error messages. * NumpyArray error messages are correct. * Have to carry knowledge of fake dimensions to give the right error message. * All cpu-kernels should return Error objects, to ensure consistency in the future. * Locations can only be used if there are Identities. * The 'fake' argument isn't necessary because fake dimensions will never have Identities. * These are good error messages. * Update the Numba side in preparation for handling errors. * Numba can raise errors in response to the Error.str value. * Raise errors in Numba, if the function we call returns them (too bad we can't have more specific messages, though). * Put the 'str' member first so that success vs failure can be determined without an offset. * Change order of 'failure' function options to highlight the leading role of the static string.
- Loading branch information
Showing
27 changed files
with
759 additions
and
236 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1 +1 @@ | ||
0.1.9 | ||
0.1.10 |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.