I think error wrapping should be done with extreme care as it exposes internals of a package in it's exported API. Is a temporary cause generating temporary errors even if 12 levels deep? Is io.EOF ok or should it be opaque? Some io functions absorbe io.EOF.
-
-
-
I mentioned this issue in the README as well. I'm planning to provide certain customizations so people have some control to decide where to change or not. The error is exposed either way. I think it's up to the people whether it's worth for them or not.
Kraj razgovora
Novi razgovor -
-
-
This is cool!!! Just in time before the holidays :)
-
Thank you Jaana
Kraj razgovora
Novi razgovor -
-
-
I think you should move main.go to the top level, so you can just go gethttp://github.com/fatih/errwrap
-
Yeah, gomodifytags is like that. I made it explicitly like that. Maybe I should make it differently.
Kraj razgovora
Novi razgovor -
-
-
What kind of shell autocomplete is this? Looks neat

-
I'm using these two zsh plugins: https://github.com/zsh-users/zsh-autosuggestions … and https://github.com/zsh-users/zsh-syntax-highlighting …. You can see the setup in my dotfiles:https://github.com/fatih/dotfiles
- Još 1 odgovor
Novi razgovor -
-
-
I have ~ 250k lines of Go for Aether Pro and 80k for Aether - you probably saved me two weeks. Thanks!
- Još 1 odgovor
Novi razgovor -
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.
Happy to announce my new tool "errwrap". A Go tool to wrap and fix errors with the new %w verb directive.