Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Use cargo-metadata #52

Open
roblabla opened this issue Dec 25, 2018 · 3 comments
Open

Use cargo-metadata #52

roblabla opened this issue Dec 25, 2018 · 3 comments
Assignees
@roblabla

Comments

@roblabla
Copy link
Owner

Discussed in #34.

Instead of using cargo as a library (leading to problems like #51), we should use a cargo wrapper (like escargot). This will give us all the benefits of using cargo-as-a-library (proper error codes, no parsing of stdout/stderr stream) without the downside of it going stale.
@roblabla roblabla mentioned this issue Dec 25, 2018
Closed
@kurnevsky kurnevsky mentioned this issue Jan 10, 2019
Merged
@roblabla roblabla self-assigned this Jun 17, 2019
@roblabla
Copy link
Owner Author

This is turning out to be complicated due to a very "dumb" problem: I can't figure out how to get either docopt or clap to give me a list of unmatched arguments. This leads me to write incredibly brittle code recreating the parameters from a full parse. Really not ideal, but I guess I'll have to live with it.

@roblabla roblabla mentioned this issue Jun 17, 2019
Open
@roblabla
Copy link
Owner Author

The absence of rust-lang/cargo#3855 is going to hurt the output a lot.

@roblabla
Copy link
Owner Author

#64

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@roblabla roblabla

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@roblabla