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.

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

Cargo: project system (and configuration) #196

Open
vosen opened this issue Oct 29, 2015 · 3 comments
Open

Cargo: project system (and configuration) #196

vosen opened this issue Oct 29, 2015 · 3 comments
Assignees

Comments

@vosen
Copy link
Member

vosen commented Oct 29, 2015

Split off from #3.
Handle Cargo.toml file in the project system (allow for Cargo.toml being placed in non-root locations). Handle loading/saving/editing of Cargo.toml though project settings

@sherry-ummen
Copy link

Hello, wanted to know. Whether this will be done any time soon. Thanks

@vosen
Copy link
Member Author

vosen commented Mar 20, 2016

Hard to tell. I'm finishing whitespace-aware toml parsing here. Once it's done Il'll have to wrap it for C# and then start modifying Visual Rust to rely on it. The work progresses but I'm giving no hard guarantees or deadlines.

@Boddlnagg
Copy link
Contributor

Boddlnagg commented Sep 21, 2017

We should probably aim to use toml_edit for editing of Cargo.toml, since @vosen's toml_document is undocumented and hasn't seen progress in the last year. Furthermore it looks like toml_edit will be used by cargo-edit (see killercup/cargo-edit#69 (comment)), so it will be sufficiently battle-tested.

We will need a C# wrapper (through a C API) which partially exists for toml_document, but it should be possible to write that for toml_edit as well. The alternative would be a .NET implementation of a TOML library that preserves formatting, which is probably much harder.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants