Zander Milroy

I feel the `&&` and `||` operators (or some variant of) are outside the scope of a single semver and would extend into the scope of a compound one. Meaning...

We could also create something that acts specifically as a collection of semantic versions? At the very least we need some kind of data structure to store the version data...

Right now, essentially the difference between a **version** and a **constraint** is defined by the result of `isSpecific()` which just tests for the presence of operator prefixes to the version....

Is it weird to possibly merge this onto a new branch instead so it's more open to contributions? It would allow for contributions while keeping it out of master until...

I rebased and dropped those 2 commits. Good call. I really like the idea of using an enum for that. I'll make some time in the next couple days to...

I pushed a number of significant changes to add the suggested `SemConstraint` enum and to allow for the creation of complex constraints using the `&&` and `||` operators. All **semantic...

I don't feel like there's a tonne of work getting this to a state where it's considered mergeable, I agree with a lot of the things pointed out by @Dr-Emann...

Hey so, I took a stab at these changes and believe I addressed the issues brought up by @Dr-Emann I encourage people to look through my test coverage and suggest...

I do agree with these points, but also I feel this is a step in a correct direction over the current implementation, which is to have absolutely no way of...

Commit 0cfc177 is related to this.