Hi guys! I just want to know the best practice here. In my package, if I see an error related to an wrong input argument (like using -1 for orbit eccentricity), then is it better to use error ou throw(ArgumentError(...)) to the user? I asked on slack but I got mixed results.

Being more specific also allows you to write tests with @test_throws that don’t just pass spuriously if the same type of error is thrown in some other part of the code under test.

`error` vs `throw(ArgumentError(...))`

General Usage

Ronis_BR December 22, 2018, 5:36pm 4

Excellent arguments! Thanks guys, I will change all the errors to some more informative.

2 Likes

Topic		Replies	Views
Style guide for throwing errors? General Usage error-message	6	1501	November 20, 2018
When ArgumentError should be thrown? General Usage question	4	2062	July 10, 2019
Best way to enforce argument requirements (assert vs. exception, or something else)? General Usage question	3	1322	April 23, 2021
Please stop using `error` and `ErrorException` in packages (and Base) General Usage error	29	6596	May 2, 2019
What's the differences between `throw(ArgumentError(""))` and `return throw(ArgumentError("")`) General Usage question , exception	1	881	December 16, 2020

`error` vs `throw(ArgumentError(...))`

Related topics