-
Notifications
You must be signed in to change notification settings - Fork 206
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
No panics #51
Comments
dig doesn't panic?
|
We actually panic recover and return an error if something blows up in a constructor as well: defer func() {
if r := recover(); r != nil {
err = fmt.Errorf("panic during Resolve %v", r)
}
}() |
we could even add the same panic recovery system to |
Ok - so we never panic, that's great. I'm actually not sure if we should recover other panics TBH, but that's a separate concern. |
The initial idea was to add them to cover reflect specific errors - it tend to panic a lot. But now that I think about it, we're also going to catch panics in constructors -- and we will return an error. And you're right, that might not be desired. Lets talk about it in another thread to see if we should drop that |
* Ignore mem and cpu files * Add check for off-master baselines. Allow to override * Colors. Colors everywhere
Dig should always return
errs
so that FX can control what thoseerrs
mean.The text was updated successfully, but these errors were encountered: