pubgrub VS crates.io

I initially spend quite some time investigating PubGrub for conda (using the awesome rust implementation) but gave up after some time. The biggest issue was that the primitive used in the pubgrub algorithm is the concept of a range and the mathematical operations you can apply to it. This makes the algorithm very good at reasoning about whether or not a particular spec is worth considering. However, it requires that you can express a set of versions as a continuous range. This is often the case when you talk about things like semver, but in conda there are many more factors to consider, for instance, a spec (matchspec in condas case) might, besides referring to a version also refer to a build string in the form of globs ("*cuda") or build numbers, different platforms, features, hashes and you can even use regular expressions in there. I have not been able to figure out a way to map conda matchspecs into a range primitive that works for pubgrub.

Note that the type system is turing complete, so NP-Hard is not so bad. :-) Also if you are interested in working on a useful NP-Hard problem in rust, we would love help with the PubGrub project!

Thanks! it's still a bit fuzzy for me but I've added an issue for this: https://github.com/pubgrub-rs/pubgrub/issues/101 and when we have the time we'll try to implement it!

I am pleased to announce elm-test-rs 1.0.0, a tests runner for the Elm language, like elm-test, mostly built in Rust. This has been a long road and it also included the implementation of the pubgrub dependency solver in Rust to re-conciliate normal and tests dependencies.

If a major pro of Iai is that it can be run in CI, then a guide to setting that up would be great! I would love to use pubgrubs as a guinea pig, if that helps.

Rust has a rich ecosystem of frameworks and libraries that let you read, parse, and manipulate text files, interact with cloud services and databases, and perform any other job that your project's development workflow may require. And because of its strong typing and tight memory management, you are much less likely to write programs that behave unexpectedly in production.

All the code discussed in this article can be accessed through this repository. For integration with existing projects consider using keyword_extraction crate available on crates.io.

So, be sure to double-check your critical libraries and be sure their alternatives exist in the Rust ecosystem. There’s a good chance the crates you need are available in Rust's crates.io repository.

The previous section was very simple, this section is also very simple but introduces us to cargo which is Rust's package manager, as a JS dev my mind goes straight to NPM.

Now, there has to be a place where all these packages come from. Similar to npmjs registry, where all node packages are registered, stored and retrieved, Rust also has something called crates.io where many helpful packages and dependencies are registered.

Before proceeding, let's check https://crates.io/, the official Rust package registry.

The most thrilling aspect has been the joy of writing the backend. It's like every struct, enum, and method in Rust forms this interconnected Multiverse of code , which you can see in crates.io which is best Documentation experience I Ever Had.

5. Crates.io

When using crates from eg. crates.io, and also things like std and core

Vendoring your packages was very tedious to even remotely get to work with Cargo. I spent a very long time getting Cargo to work together with cargo-local-registry. We vendor crates from crates.io and a custom internal registry.