Add assert_only_contains_regex!

[mgeisler]

This macro compliments the existing assert_contains_regex!. While assert_contains_regex! implements the “exists” quantifier, the new macro implements a “for all” quantifier.

In more details, the macro uses two steps:

1. Replace {version} in the template by a regular expression which will match any SemVer version number. This allows, say, docs.rs/{name}/{version}/ to match old and outdated occurrences of your package.

2. Find all matches in the file and check each match against template. This time we replace {version} with pkg_version so that we can do an accurate comparison with the actual package version.

This allows you to ensure that, say, all docs.rs links are updated.

Fixes #72.

[mgeisler]

Hi @alecmocatta, I looked at #72 and this PR should implement your idea. If you're still interested, then please let me know if this does what you expect. Thanks!

[alecmocatta]

Thanks for the ping @mgeisler!

Yeah this addresses exactly what I was looking for, so many thanks and I look forward to adopting it!

One thing maybe worth considering is accepting abridged semver versions where they're "compatible", e.g. permitting https://docs.rs/serde/1/serde/trait.Deserialize.html for version numbers 1.*.*. Per https://doc.rust-lang.org/cargo/reference/semver.html "only changes in the left-most non-zero component are considered incompatible".

[mgeisler]

One thing maybe worth considering is accepting abridged semver versions where they're "compatible", e.g. permitting https://docs.rs/serde/1/serde/trait.Deserialize.html for version numbers 1.*.*. Per https://doc.rust-lang.org/cargo/reference/semver.html "only changes in the left-most non-zero component are considered incompatible".

Oh, that's a good idea, let me see if I can implement this somehow!

[mgeisler]

Okay, I've pushed a new version which compares the versions in the same way as the other macros: so 1.2 is now seen as being compatible with {version} when the package version is 1.2.3. Seems to work pretty well.