Currently the project throws quite a lot of RuntimeExceptions (also in native code). This makes it hard for the user to handle different exception types in different ways and the exception type itself is not very meaningful.
It might be good to redesign the API and create custom exception types, ideally checked ones since when dealing with native code unexpected things might happen and the caller should be required to handle those (?).
Maybe it would be good to target these (breaking) changes for version 2.0.0?
Currently the project throws quite a lot of
RuntimeExceptions (also in native code). This makes it hard for the user to handle different exception types in different ways and the exception type itself is not very meaningful.It might be good to redesign the API and create custom exception types, ideally checked ones since when dealing with native code unexpected things might happen and the caller should be required to handle those (?).
Maybe it would be good to target these (breaking) changes for version 2.0.0?