Jeff Walker

I had the same confusion when I was first looking at this package. I at first thought that it would make sense that `new semver.Range(range, { includePrerelease: true})` included all...

@kokushkin you did not quote the relevant part of the semver.org spec > 4. Major version zero (0.y.z) is for initial development. Anything MAY change at any time. The public...

@damepatr To help me understand the use case and how to best address it, how are you getting patch numbers so high? Also, what is the highest patch number you...

A preview of this feature has been released in the `3.0.0-beta.0` version available on NuGet.

This has been fixed on master and will be included in v3.0.0

I'm getting the same error. Would really like to try out champ, but can't because of this.

I'm not able to reproduce this on Windows 7 using tup v0.7.6-18-gb22cb9e

My previous argument was based on the effect when not doing an atomic wait. I just needed to actually do an atomic wait for real and found some additional concerns....

The `SemVersionRange.TryParseNpm` function is specifically meant to match npm supported range syntax. I wouldn't expect it to support any other syntax. Unfortunately, adding support for `!=` to the standard range...

The one case where it might make sense to allow them to be true expression is some kind of null coalesce like `foo ?? => value`. But that seems unusual...