| Age | Commit message (Collapse) | Author | Lines | |
|---|---|---|---|---|
| 2023-01-11 | Move /src/test to /tests | Albert Larsan | -712/+0 | |
| 2022-12-14 | Added PlayStation Vita support | Andrés Martínez | -1/+1 | |
| 2022-11-17 | Add powerpc64-ibm-aix as Tier-3 target | Qiu Chaofan | -1/+1 | |
| 2022-11-11 | Add `nto` as known `target_os` | Florian Bartels | -1/+1 | |
| 2022-10-01 | bless ui tests | Maybe Waffle | -5/+5 | |
| 2022-09-02 | Add warning against unexpected --cfg with --check-cfg | Urgau | -3/+23 | |
| 2022-08-31 | Fix ci checks | Dezhi Wu | -2/+2 | |
| 2022-07-20 | Remove implicit names and values from --cfg in --check-cfg | Urgau | -38/+63 | |
| 2022-06-13 | Add Apple WatchOS compile targets | Vladimir Michael Eatwell | -1/+1 | |
| 2022-06-04 | test: add `xous` to well-known-values.stderr | Sean Cross | -1/+1 | |
| Signed-off-by: Sean Cross <sean@xobs.io> | ||||
| 2022-05-24 | RFC3239: Add tests for compact `cfg(target(..))` | Loïc BRANSTETT | -0/+51 | |
| 2022-03-19 | Extend --check-cfg tests to all predicate inside all/any | Loïc BRANSTETT | -1/+117 | |
| 2022-03-09 | Add miri to the well known conditional compilation names and values | Loïc BRANSTETT | -1/+41 | |
| 2022-03-05 | Improve unexpected_cfgs lint when their is no value expected | Loïc BRANSTETT | -4/+22 | |
| 2022-03-04 | Rollup merge of #94362 - Urgau:check-cfg-values, r=petrochenkov | Dylan DPC | -3/+75 | |
| Add well known values to `--check-cfg` implementation This pull-request adds well known values for the well known names via `--check-cfg=values()`. [RFC 3013: Checking conditional compilation at compile time](https://rust-lang.github.io/rfcs/3013-conditional-compilation-checking.html#checking-conditional-compilation-at-compile-time) doesn't define this at all, but this seems a nice improvement. The activation is done by a empty `values()` (new syntax) similar to `names()` except that `names(foo)` also activate well known names while `values(aa, "aa", "kk")` would not. As stated this use a different activation logic because well known values for the well known names are not always sufficient. In fact this is problematic for every `target_*` cfg because of non builtin targets, as the current implementation use those built-ins targets to create the list the well known values. The implementation is straight forward, first we gather (if necessary) all the values (lazily or not) and then we apply them. r? ```@petrochenkov``` | ||||
| 2022-03-04 | Add well known values to --check-cfg implementation | Loïc BRANSTETT | -1/+75 | |
| 2022-03-03 | Add support for values() with --check-cfg | Loïc BRANSTETT | -4/+2 | |
| 2022-03-03 | Fix invalid lint_node_id being put on a removed stmt | Loïc BRANSTETT | -0/+20 | |
| 2022-03-01 | Improve allowness of the unexpected_cfgs lint | Loïc BRANSTETT | -0/+62 | |
| 2022-02-23 | Continue improvements on the --check-cfg implementation | Loïc BRANSTETT | -1/+138 | |
| - Test the combinations of --check-cfg with partial values() and --cfg - Test that we detect unexpected value when none are expected | ||||
| 2022-02-22 | Improve diagnostic of the unexpected_cfgs lint | Loïc BRANSTETT | -4/+9 | |
| 2022-02-22 | Add test for well known names defined by rustc | Loïc BRANSTETT | -0/+49 | |
| 2022-02-16 | Implement --check-cfg option (RFC 3013) | Loïc BRANSTETT | -0/+97 | |
| Co-authored-by: Urgau <lolo.branstett@numericable.fr> Co-authored-by: Marcelina Kościelnicka <mwk@0x04.net> | ||||
 |
index : rust | |
| https://github.com/rust-lang/rust |
| about summary refs log tree commit diff |