{"push_id":1651694139,"size":5,"distinct_size":1,"ref":"refs/heads/fix-3499","head":"6a74da1af37e19c35f99bb97952dfc55ee3fad3f","before":"8bdfbb7f4b514a40a0efbe78ad227067ccb57f09","commits":[{"sha":"83dc9406f346726ca296bd8da6fb6eb4561d3897","author":{"name":"Aleksey Kladov","email":"856288be0fcd275a8d63ef799292eb44a691c49c@gmail.com"},"message":"Fix false positive about unused replace","distinct":false,"url":"https://api.github.com/repos/tee-too/cargo/commits/83dc9406f346726ca296bd8da6fb6eb4561d3897"},{"sha":"25e50b58042fc59297a0e6165d1ea5a08f889973","author":{"name":"James Bendig","email":"da0df48474d987bed3657405bede20dcfce53b44@starbytesoftware.com"},"message":"Fix `cargo run` panic when required-features not satisfied\n\nFixes #3867","distinct":false,"url":"https://api.github.com/repos/tee-too/cargo/commits/25e50b58042fc59297a0e6165d1ea5a08f889973"},{"sha":"e28f5cb8c5688cd95e2f00330e5fc0a3fc7331b1","author":{"name":"bors","email":"f85d84007542459f7a0e8d187f971eeac8d04314@rust-lang.org"},"message":"Auto merge of #3879 - jbendig:issue_3867, r=alexcrichton\n\nFix `cargo run` panic when required-features not satisfied\n\nThis PR fixes #3867 which is made up of two parts.\n\nThe first part involves `cargo run` triggering an assertion after compiling. This is triggered by the single binary selected for compilation being filtered out when required-features is specified and said features are not enabled. The cleanest approach to me involves just sticking a flag into `CompileFilter::Everything`. The flag then triggers the already existing error message when required-features is not satisfied. I think this works best because it localizes what is really a `cargo run` quirk without requiring any boilerplate or duplicate code.\n\nThe second part shows `cargo run` bailing when two binaries exist, both with required-features, but only one is resolved to be compiled due to default features. I feel like the current approach is correct because it's consistent with what normally happens when there are multiple binaries. I'm open to changing this, but for now, I've added a test to enforce this behavior.\n\ncc @BenWiederhake: I took a quick peek at your branch to fix #3112 and I noticed that it probably won't merge cleanly with this PR. Just an FYI in case it makes sense to have this merged.","distinct":false,"url":"https://api.github.com/repos/tee-too/cargo/commits/e28f5cb8c5688cd95e2f00330e5fc0a3fc7331b1"},{"sha":"3191040012723f6d5b4f790c0a712d2b1f1132ab","author":{"name":"bors","email":"f85d84007542459f7a0e8d187f971eeac8d04314@rust-lang.org"},"message":"Auto merge of #3875 - matklad:unused-replace, r=alexcrichton\n\nFix false positive about unused replace\n\ncloses #3861\n@chriscoomber thanks for the great repro!","distinct":false,"url":"https://api.github.com/repos/tee-too/cargo/commits/3191040012723f6d5b4f790c0a712d2b1f1132ab"},{"sha":"6a74da1af37e19c35f99bb97952dfc55ee3fad3f","author":{"name":"tee-too","email":"c9f04ebaaa68984b5fc0d3f08f155c34ab6ee852@users.noreply.github.com"},"message":"Add `[target.'cfg(...)']` syntax for rustc(doc)flags in .cargo/config\n\nAllow to use the Rust `cfg(...)` syntax to configure rust(doc)flags.\nThe flags are concatenated when a build matches several `cfg`, or\nseveral `cfg` and a $triple.\n\nFix #3499.","distinct":true,"url":"https://api.github.com/repos/tee-too/cargo/commits/6a74da1af37e19c35f99bb97952dfc55ee3fad3f"}]}
{"actor":{"display_login":"tee-too"}}