Consider '=' constraint implicit if operator is missing [experimental]

[cmaglie]

This allows parsing of constraints like 1.0.0 as =1.0.0.
Any other combination is allowed too 1.0.0 && 1.0.1 now means =1.0.0 && =1.0.1

[codecov]

Codecov Report

Merging #7 (17ed0f5) into master (2f82020) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master       #7   +/-   ##
=======================================
  Coverage   99.84%   99.84%           
=======================================
  Files           9        9           
  Lines         651      660    +9     
=======================================
+ Hits          650      659    +9     
  Misses          1        1           

Impacted Files	Coverage Δ
constraints.go	100.00% <100.00%> (ø)

---

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 2f82020...17ed0f5. Read the comment docs.

[per1234]

I suggest adding another row to the table in the readme:

diff --git a/README.md b/README.md
index 1419c81..d23c58c 100644
--- a/README.md
+++ b/README.md
@@ -64,6 +64,7 @@ constraints would resolve as follows:
 | Constraint                       | Resolution |
 | -------------------------------- | ---------- |
 | `=1.0.0`                         | `1.0.0`    |
+| `1.0.0`                          | `1.0.0`    |
 | `>1.0.0`                         | `2.1.0`    |
 | `>=1.0.0`                        | `2.1.0`    |
 | `<2.0.0`                         | `1.0.0`    |

I think that would provide sufficient documentation coverage of the new capability.

[cmaglie]

Superseded by #10