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

make sure to review a new RFC #54

Closed
johnynek opened this issue Sep 1, 2017 · 1 comment
Closed

make sure to review a new RFC #54

johnynek opened this issue Sep 1, 2017 · 1 comment

Comments

@johnynek
Copy link
Member

johnynek commented Sep 1, 2017

rust-lang/rfcs#2136

This explicitly mentions bazel. Someone from this project should review that RFC and make sure any obvious points are missed.

@acmcarther
Copy link
Collaborator

Back when that RFC was active, I dropped my two cents in there. It happens that I took quite a lot of what was suggested (specifically specifying customizations in the Cargo.toml) and implemented these into google/cargo-raze as a [raze] section.

That said, I didn't really fulfill the spirit of that RFC -- good interaction with the standard tools. There are some discussions happening to claw some of that back (#71 comes to mind), but I harbor a huge amount of pessimism that we can (or should!) impose our constraints on the Rust ecosystem as a whole.

With that said, I'm going to close this for now as I don't see any next steps for this issue. I'm definitely going to keep an eye on how this moves forward Rust-side though. Please reopen if I missed anything!

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

No branches or pull requests

2 participants