mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
1393ef1fa0
rust/tests/ui/const-generics/std/const-generics-range.min.stderr

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

57 lines
2.4 KiB
Plaintext
Raw Normal View History

Added a lot of min_const_generics revisions
2020-08-26 05:22:55 -05:00
error: `std::ops::Range<usize>` is forbidden as the type of a const generic parameter
Implement custom diagnostic for ConstParamTy
2023-05-16 23:05:46 -05:00
--> $DIR/const-generics-range.rs:8:24
Added a lot of min_const_generics revisions
2020-08-26 05:22:55 -05:00
|
LL | struct _Range<const R: std::ops::Range<usize>>;
| ^^^^^^^^^^^^^^^^^^^^^^
|
= note: the only supported types are integers, `bool` and `char`
`feature(const_param_types)` -> `feature(adt_const_params)`
2021-08-30 03:59:53 -05:00
= help: more complex types are supported with `#![feature(adt_const_params)]`
Added a lot of min_const_generics revisions
2020-08-26 05:22:55 -05:00
pretty: trim paths of unique symbols If a symbol name can only be imported from one place for a type, and as long as it was not glob-imported anywhere in the current crate, we can trim its printed path and print only the name. This has wide implications on error messages with types, for example, shortening `std::vec::Vec` to just `Vec`, as long as there is no other `Vec` importable anywhere. This adds a new '-Z trim-diagnostic-paths=false' option to control this feature. On the good path, with no diagnosis printed, we should try to avoid issuing this query, so we need to prevent trimmed_def_paths query on several cases. This change also relies on a previous commit that differentiates between `Debug` and `Display` on various rustc types, where the latter is trimmed and presented to the user and the former is not.
2020-09-02 02:40:56 -05:00
error: `RangeFrom<usize>` is forbidden as the type of a const generic parameter
Implement custom diagnostic for ConstParamTy
2023-05-16 23:05:46 -05:00
--> $DIR/const-generics-range.rs:13:28
Added a lot of min_const_generics revisions
2020-08-26 05:22:55 -05:00
|
LL | struct _RangeFrom<const R: std::ops::RangeFrom<usize>>;
| ^^^^^^^^^^^^^^^^^^^^^^^^^^
|
= note: the only supported types are integers, `bool` and `char`
`feature(const_param_types)` -> `feature(adt_const_params)`
2021-08-30 03:59:53 -05:00
= help: more complex types are supported with `#![feature(adt_const_params)]`
Added a lot of min_const_generics revisions
2020-08-26 05:22:55 -05:00
pretty: trim paths of unique symbols If a symbol name can only be imported from one place for a type, and as long as it was not glob-imported anywhere in the current crate, we can trim its printed path and print only the name. This has wide implications on error messages with types, for example, shortening `std::vec::Vec` to just `Vec`, as long as there is no other `Vec` importable anywhere. This adds a new '-Z trim-diagnostic-paths=false' option to control this feature. On the good path, with no diagnosis printed, we should try to avoid issuing this query, so we need to prevent trimmed_def_paths query on several cases. This change also relies on a previous commit that differentiates between `Debug` and `Display` on various rustc types, where the latter is trimmed and presented to the user and the former is not.
2020-09-02 02:40:56 -05:00
error: `RangeFull` is forbidden as the type of a const generic parameter
Implement custom diagnostic for ConstParamTy
2023-05-16 23:05:46 -05:00
--> $DIR/const-generics-range.rs:18:28
Added a lot of min_const_generics revisions
2020-08-26 05:22:55 -05:00
|
LL | struct _RangeFull<const R: std::ops::RangeFull>;
| ^^^^^^^^^^^^^^^^^^^
|
= note: the only supported types are integers, `bool` and `char`
`feature(const_param_types)` -> `feature(adt_const_params)`
2021-08-30 03:59:53 -05:00
= help: more complex types are supported with `#![feature(adt_const_params)]`
Added a lot of min_const_generics revisions
2020-08-26 05:22:55 -05:00
pretty: trim paths of unique symbols If a symbol name can only be imported from one place for a type, and as long as it was not glob-imported anywhere in the current crate, we can trim its printed path and print only the name. This has wide implications on error messages with types, for example, shortening `std::vec::Vec` to just `Vec`, as long as there is no other `Vec` importable anywhere. This adds a new '-Z trim-diagnostic-paths=false' option to control this feature. On the good path, with no diagnosis printed, we should try to avoid issuing this query, so we need to prevent trimmed_def_paths query on several cases. This change also relies on a previous commit that differentiates between `Debug` and `Display` on various rustc types, where the latter is trimmed and presented to the user and the former is not.
2020-09-02 02:40:56 -05:00
error: `RangeInclusive<usize>` is forbidden as the type of a const generic parameter
Implement custom diagnostic for ConstParamTy
2023-05-16 23:05:46 -05:00
--> $DIR/const-generics-range.rs:24:33
Added a lot of min_const_generics revisions
2020-08-26 05:22:55 -05:00
|
LL | struct _RangeInclusive<const R: std::ops::RangeInclusive<usize>>;
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
= note: the only supported types are integers, `bool` and `char`
`feature(const_param_types)` -> `feature(adt_const_params)`
2021-08-30 03:59:53 -05:00
= help: more complex types are supported with `#![feature(adt_const_params)]`
Added a lot of min_const_generics revisions
2020-08-26 05:22:55 -05:00
pretty: trim paths of unique symbols If a symbol name can only be imported from one place for a type, and as long as it was not glob-imported anywhere in the current crate, we can trim its printed path and print only the name. This has wide implications on error messages with types, for example, shortening `std::vec::Vec` to just `Vec`, as long as there is no other `Vec` importable anywhere. This adds a new '-Z trim-diagnostic-paths=false' option to control this feature. On the good path, with no diagnosis printed, we should try to avoid issuing this query, so we need to prevent trimmed_def_paths query on several cases. This change also relies on a previous commit that differentiates between `Debug` and `Display` on various rustc types, where the latter is trimmed and presented to the user and the former is not.
2020-09-02 02:40:56 -05:00
error: `RangeTo<usize>` is forbidden as the type of a const generic parameter
Implement custom diagnostic for ConstParamTy
2023-05-16 23:05:46 -05:00
--> $DIR/const-generics-range.rs:29:26
Added a lot of min_const_generics revisions
2020-08-26 05:22:55 -05:00
|
LL | struct _RangeTo<const R: std::ops::RangeTo<usize>>;
| ^^^^^^^^^^^^^^^^^^^^^^^^
|
= note: the only supported types are integers, `bool` and `char`
`feature(const_param_types)` -> `feature(adt_const_params)`
2021-08-30 03:59:53 -05:00
= help: more complex types are supported with `#![feature(adt_const_params)]`
Added a lot of min_const_generics revisions
2020-08-26 05:22:55 -05:00
pretty: trim paths of unique symbols If a symbol name can only be imported from one place for a type, and as long as it was not glob-imported anywhere in the current crate, we can trim its printed path and print only the name. This has wide implications on error messages with types, for example, shortening `std::vec::Vec` to just `Vec`, as long as there is no other `Vec` importable anywhere. This adds a new '-Z trim-diagnostic-paths=false' option to control this feature. On the good path, with no diagnosis printed, we should try to avoid issuing this query, so we need to prevent trimmed_def_paths query on several cases. This change also relies on a previous commit that differentiates between `Debug` and `Display` on various rustc types, where the latter is trimmed and presented to the user and the former is not.
2020-09-02 02:40:56 -05:00
error: `RangeToInclusive<usize>` is forbidden as the type of a const generic parameter
Implement custom diagnostic for ConstParamTy
2023-05-16 23:05:46 -05:00
--> $DIR/const-generics-range.rs:34:35
Added a lot of min_const_generics revisions
2020-08-26 05:22:55 -05:00
|
LL | struct _RangeToInclusive<const R: std::ops::RangeToInclusive<usize>>;
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
= note: the only supported types are integers, `bool` and `char`
`feature(const_param_types)` -> `feature(adt_const_params)`
2021-08-30 03:59:53 -05:00
= help: more complex types are supported with `#![feature(adt_const_params)]`
Added a lot of min_const_generics revisions
2020-08-26 05:22:55 -05:00
error: aborting due to 6 previous errors
Reference in New Issue Copy Permalink