File tree Expand file tree Collapse file tree 1 file changed +2
-6
lines changed Expand file tree Collapse file tree 1 file changed +2
-6
lines changed Original file line number Diff line number Diff line change @@ -363,10 +363,8 @@ The responsibilities of Cargo:
363
363
## Implmentation strategy: Leverage JSON error-format
364
364
365
365
The cleanest way to implement the above division of responsbilities
366
- without perturbing * non-cargo* uses of ` rustc ` is probably to make two changes:
367
-
368
- * Cargo should * always* use ` --error-format=json ` for its ` rustc `
369
- invocations, and
366
+ without perturbing * non-cargo* uses of ` rustc ` is probably to make
367
+ the following change:
370
368
371
369
* ` rustc ` should treat ` --error-format=json ` as signal that it should
372
370
emit a future-incompatibility summary report for the crate.
@@ -586,8 +584,6 @@ I have not explicitly addressed nor seriously investigated this.
586
584
587
585
* Is using ` --error-format=json ` as the way to switch ` rustc ` into the future-incompatibility checking mode reasonable?
588
586
589
- * Is turning on ` --error-format=json ` by default everywhere in ` cargo ` reasonable?
590
-
591
587
# Future possibilities
592
588
[ future-possibilities ] : #future-possibilities
593
589
You can’t perform that action at this time.
0 commit comments