-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
document arguments to exception constructors #7766
Comments
The no method errors are because some of them take string arguments as the error message to be shown to the user. |
@quinnj That makes sense. I could either update the docs indicating which ones take strings, or add uninitialized constructors. The former sounds better to me. What do you think? |
Adding docs for how things are currently is always a 'yes' 😄 My guess is these methods weren't given a no-arg constructor on purpose; to make sure an explanation goes along with the exception. See also #4744 and a bunch of other threads linked to from there. |
There are help entries for those exception types, but they're documented as variables instead of functions, so their arguments are not documented. This should be fixed in |
…rs. [ci skip] Closes JuliaLang#7766. Also update helpdb.jl.
…rs. [ci skip] Closes JuliaLang#7766. Also update helpdb.jl.
…rs. [ci skip] Closes JuliaLang#7766. Also update helpdb.jl.
in : http://docs.julialang.org/en/latest/manual/control-flow/#built-in-exceptions
It looks like these are all being exported in https://github.com/JuliaLang/julia/blob/c7fb8f5be03edd30598ef49f10d175601690f997/base/exports.jl
Am I doing something wrong?
The text was updated successfully, but these errors were encountered: