You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 13, 2019. It is now read-only.
Setting aside the technical challenge, rusti could know about cargo and fetch built dependencies/the project itself when asked, besides just the std crates.
The text was updated successfully, but these errors were encountered:
I like this idea. If Cargo had a command that would download and build a crate by name given on the command line, I think the rest would be fairly straightforward.
Setting aside the technical challenge, rusti could know about cargo and fetch built dependencies/the project itself when asked, besides just the std crates.
It would cause too much trouble to create some temporal cargo crate to manage this? It would be possible to generate the dependencies and inject them into Cargo.toml for example and then just compile them (just throwing the idea, don't know if it would work)
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Setting aside the technical challenge, rusti could know about cargo and fetch built dependencies/the project itself when asked, besides just the std crates.
The text was updated successfully, but these errors were encountered: