Skip to content
This repository has been archived by the owner on Jul 13, 2019. It is now read-only.

Load other crates #2

Open
reem opened this issue Dec 16, 2014 · 5 comments
Open

Load other crates #2

reem opened this issue Dec 16, 2014 · 5 comments
Labels

Comments

@reem
Copy link

reem commented Dec 16, 2014

Setting aside the technical challenge, rusti could know about cargo and fetch built dependencies/the project itself when asked, besides just the std crates.

@murarth
Copy link
Owner

murarth commented Dec 17, 2014

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.

@max6cn
Copy link

max6cn commented Apr 16, 2015

Setting aside the technical challenge, rusti could know about cargo and fetch built dependencies/the project itself when asked, besides just the std crates.

+1 on this feature

@ghost
Copy link

ghost commented Oct 19, 2015

I also would be interested in this feature, otherwise I will have to write tests!

@nixpulvis
Copy link

being able to play around with my functions and types as I develop would be pretty awesome.

@ghost
Copy link

ghost commented Apr 24, 2017

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 free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

4 participants