Fix unhandled errors

[im-kulikov]

---

cc @alexaandru / @vishr

[codecov]

Codecov Report

Merging #1271 into master will decrease coverage by 0.09%.
The diff coverage is 33.33%.

@@            Coverage Diff            @@
##           master    #1271     +/-   ##
=========================================
- Coverage   81.88%   81.78%   -0.1%     
=========================================
  Files          26       26             
  Lines        1932     1933      +1     
=========================================
- Hits         1582     1581      -1     
- Misses        242      243      +1     
- Partials      108      109      +1

Impacted Files	Coverage Δ
echo.go	86.95% <33.33%> (-0.68%)	⬇️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 6d9e043...26eb8c8. Read the comment docs.

[alexaandru]

LGTM but I do have one question:

Now that we have modules support, things have changed quite a bit:

BEFORE: go get ... would pull the latest master, so if we pushed changes/fixes, people could still fetch them even if we did not cut a release.

NOW: with Go modules support, people using Go modules can only pull tagged releases (well, they can forge a given commit but that is ugly). So what does this mean in practice?!? Do we create release (and a tag) after every single commit? :-) That'll be a bit weird... Thoughts @im-kulikov @vishr ?

[im-kulikov]

if someone needs a specific release, he can get it:
go get <url>:@<version>
or
go get <url>:@latest

Master branch is under development, and not for use.. (IMO)..

once we have collected a critical number of fixes, we can prepare a release. there's nothing wrong with that.

---

I didn't think you'd create a v4 right away

[alexaandru]

Yup, I guess you're right. It's how it worked so far as well. Alright then, merge away please! :)

[im-kulikov]

@vishr what you think about PR?