Add support for encoding.TextUnmarshaler in bind.

[gdamore]

This permits types that already implement encoding.TextUnmarshaler (such time.Time) to automatically be supported as parameters. Types that implement the BindUnmarshaler interface use that API in preference, but having the fallback greatly reduces the effort in using time.Time in particular, and probably a number of other types besides. This change is contributed by RackTop Systems -- if there is a way to acknowledge that in a copyright statement it should read "Copyright 2019 RackTop Systems".

[codecov]

Codecov Report

Merging #1314 into master will increase coverage by 0.18%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #1314      +/-   ##
==========================================
+ Coverage   84.27%   84.45%   +0.18%     
==========================================
  Files          27       27              
  Lines        1990     2001      +11     
==========================================
+ Hits         1677     1690      +13     
+ Misses        205      203       -2     
  Partials      108      108

Impacted Files	Coverage Δ
bind.go	90.85% <100%> (+1.83%)	⬆️

---

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 e3717be...3de4ae4. Read the comment docs.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[gdamore]

Wow. Is this project still alive even?

[gdamore]

As a contributor, let me comment here. We spent effort to produce a fix (which is a real problem for us). I can understand if someone actively chose to reject the PR, or asked us to update to newer code, or make some other changes. But to be marked "stale" and "wontfix" by some bot for inactivity on an otherwise well-formed PR is really really infuriating -- it smacks of complete disrespect to potential contributors.

To be clear, I run many open source projects myself, and I don't always respond to every PR in a timely fashion, and sometimes I reject PRs. But the idea of having a bot go and reap issues that I haven't even bothered to look at myself (or haven't gotten time to look at yet) is one of the most ludicrous policies I've ever heard of.

[vishr]

@gdamore I apologize for the bot. I am trying to be more active now.

[gdamore]

Thanks!