mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
3088c4b046
rust/tests/ui/higher-ranked/higher-lifetime-bounds.stderr

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

69 lines
2.4 KiB
Plaintext
Raw Normal View History

make bounds on higher-kinded lifetimes a hard error in ast_validation Also move the check for not having type parameters into ast_validation. I was not sure what to do with compile-fail/issue-23046.rs: The issue looks like maybe the bounds actually played a role in triggering the ICE, but that seems unlikely given that the compiler seems to entirely ignore them. However, I couldn't find a testcase without the bounds, so I figured the best I could do is to just remove the bounds and make sure at least that keeps working.
2018-03-06 04:22:24 -06:00
error: lifetime bounds cannot be used in this context
Remove licenses
2018-12-25 09:56:47 -06:00
--> $DIR/higher-lifetime-bounds.rs:8:22
Warn about more ignored bounds on type aliases
2018-02-05 14:20:57 -06:00
|
make bounds on higher-kinded lifetimes a hard error in ast_validation Also move the check for not having type parameters into ast_validation. I was not sure what to do with compile-fail/issue-23046.rs: The issue looks like maybe the bounds actually played a role in triggering the ICE, but that seems unlikely given that the compiler seems to entirely ignore them. However, I couldn't find a testcase without the bounds, so I figured the best I could do is to just remove the bounds and make sure at least that keeps working.
2018-03-06 04:22:24 -06:00
LL | f: for<'xa, 'xb: 'xa+'xa> fn(&'xa i32, &'xb i32) -> &'xa i32)
| ^^^ ^^^
add lint to detect ignored generic bounds; this subsumes the previous 'generic bounds in type aliases are ignored' warning
2018-02-18 12:40:35 -06:00
make bounds on higher-kinded lifetimes a hard error in ast_validation Also move the check for not having type parameters into ast_validation. I was not sure what to do with compile-fail/issue-23046.rs: The issue looks like maybe the bounds actually played a role in triggering the ICE, but that seems unlikely given that the compiler seems to entirely ignore them. However, I couldn't find a testcase without the bounds, so I figured the best I could do is to just remove the bounds and make sure at least that keeps working.
2018-03-06 04:22:24 -06:00
error: lifetime bounds cannot be used in this context
Remove licenses
2018-12-25 09:56:47 -06:00
--> $DIR/higher-lifetime-bounds.rs:16:34
add lint to detect ignored generic bounds; this subsumes the previous 'generic bounds in type aliases are ignored' warning
2018-02-18 12:40:35 -06:00
|
LL | fn bar2<'a, 'b, F: for<'xa, 'xb: 'xa> Fn(&'xa i32, &'xb i32) -> &'xa i32>(
| ^^^
make bounds on higher-kinded lifetimes a hard error in ast_validation Also move the check for not having type parameters into ast_validation. I was not sure what to do with compile-fail/issue-23046.rs: The issue looks like maybe the bounds actually played a role in triggering the ICE, but that seems unlikely given that the compiler seems to entirely ignore them. However, I couldn't find a testcase without the bounds, so I figured the best I could do is to just remove the bounds and make sure at least that keeps working.
2018-03-06 04:22:24 -06:00
error: lifetime bounds cannot be used in this context
Remove licenses
2018-12-25 09:56:47 -06:00
--> $DIR/higher-lifetime-bounds.rs:31:28
add lint to detect ignored generic bounds; this subsumes the previous 'generic bounds in type aliases are ignored' warning
2018-02-18 12:40:35 -06:00
|
LL | where F: for<'xa, 'xb: 'xa> Fn(&'xa i32, &'xb i32) -> &'xa i32
| ^^^
make bounds on higher-kinded lifetimes a hard error in ast_validation Also move the check for not having type parameters into ast_validation. I was not sure what to do with compile-fail/issue-23046.rs: The issue looks like maybe the bounds actually played a role in triggering the ICE, but that seems unlikely given that the compiler seems to entirely ignore them. However, I couldn't find a testcase without the bounds, so I figured the best I could do is to just remove the bounds and make sure at least that keeps working.
2018-03-06 04:22:24 -06:00
error: lifetime bounds cannot be used in this context
Remove licenses
2018-12-25 09:56:47 -06:00
--> $DIR/higher-lifetime-bounds.rs:43:25
add lint to detect ignored generic bounds; this subsumes the previous 'generic bounds in type aliases are ignored' warning
2018-02-18 12:40:35 -06:00
|
LL | where for<'xa, 'xb: 'xa> F: Fn(&'xa i32, &'xb i32) -> &'xa i32
| ^^^
make bounds on higher-kinded lifetimes a hard error in ast_validation Also move the check for not having type parameters into ast_validation. I was not sure what to do with compile-fail/issue-23046.rs: The issue looks like maybe the bounds actually played a role in triggering the ICE, but that seems unlikely given that the compiler seems to entirely ignore them. However, I couldn't find a testcase without the bounds, so I figured the best I could do is to just remove the bounds and make sure at least that keeps working.
2018-03-06 04:22:24 -06:00
error: lifetime bounds cannot be used in this context
Remove licenses
2018-12-25 09:56:47 -06:00
--> $DIR/higher-lifetime-bounds.rs:51:28
add lint to detect ignored generic bounds; this subsumes the previous 'generic bounds in type aliases are ignored' warning
2018-02-18 12:40:35 -06:00
|
LL | struct S1<F: for<'xa, 'xb: 'xa> Fn(&'xa i32, &'xb i32) -> &'xa i32>(F);
| ^^^
make bounds on higher-kinded lifetimes a hard error in ast_validation Also move the check for not having type parameters into ast_validation. I was not sure what to do with compile-fail/issue-23046.rs: The issue looks like maybe the bounds actually played a role in triggering the ICE, but that seems unlikely given that the compiler seems to entirely ignore them. However, I couldn't find a testcase without the bounds, so I figured the best I could do is to just remove the bounds and make sure at least that keeps working.
2018-03-06 04:22:24 -06:00
error: lifetime bounds cannot be used in this context
Remove licenses
2018-12-25 09:56:47 -06:00
--> $DIR/higher-lifetime-bounds.rs:53:40
add lint to detect ignored generic bounds; this subsumes the previous 'generic bounds in type aliases are ignored' warning
2018-02-18 12:40:35 -06:00
|
LL | struct S2<F>(F) where F: for<'xa, 'xb: 'xa> Fn(&'xa i32, &'xb i32) -> &'xa i32;
| ^^^
make bounds on higher-kinded lifetimes a hard error in ast_validation Also move the check for not having type parameters into ast_validation. I was not sure what to do with compile-fail/issue-23046.rs: The issue looks like maybe the bounds actually played a role in triggering the ICE, but that seems unlikely given that the compiler seems to entirely ignore them. However, I couldn't find a testcase without the bounds, so I figured the best I could do is to just remove the bounds and make sure at least that keeps working.
2018-03-06 04:22:24 -06:00
error: lifetime bounds cannot be used in this context
Remove licenses
2018-12-25 09:56:47 -06:00
--> $DIR/higher-lifetime-bounds.rs:55:37
add lint to detect ignored generic bounds; this subsumes the previous 'generic bounds in type aliases are ignored' warning
2018-02-18 12:40:35 -06:00
|
LL | struct S3<F>(F) where for<'xa, 'xb: 'xa> F: Fn(&'xa i32, &'xb i32) -> &'xa i32;
| ^^^
make bounds on higher-kinded lifetimes a hard error in ast_validation Also move the check for not having type parameters into ast_validation. I was not sure what to do with compile-fail/issue-23046.rs: The issue looks like maybe the bounds actually played a role in triggering the ICE, but that seems unlikely given that the compiler seems to entirely ignore them. However, I couldn't find a testcase without the bounds, so I figured the best I could do is to just remove the bounds and make sure at least that keeps working.
2018-03-06 04:22:24 -06:00
error: lifetime bounds cannot be used in this context
Remove licenses
2018-12-25 09:56:47 -06:00
--> $DIR/higher-lifetime-bounds.rs:58:29
add lint to detect ignored generic bounds; this subsumes the previous 'generic bounds in type aliases are ignored' warning
2018-02-18 12:40:35 -06:00
|
LL | struct S_fnty(for<'xa, 'xb: 'xa> fn(&'xa i32, &'xb i32) -> &'xa i32);
| ^^^
make bounds on higher-kinded lifetimes a hard error in ast_validation Also move the check for not having type parameters into ast_validation. I was not sure what to do with compile-fail/issue-23046.rs: The issue looks like maybe the bounds actually played a role in triggering the ICE, but that seems unlikely given that the compiler seems to entirely ignore them. However, I couldn't find a testcase without the bounds, so I figured the best I could do is to just remove the bounds and make sure at least that keeps working.
2018-03-06 04:22:24 -06:00
error: lifetime bounds cannot be used in this context
Update ui test suite to use dyn
2019-05-28 13:46:13 -05:00
--> $DIR/higher-lifetime-bounds.rs:61:33
add lint to detect ignored generic bounds; this subsumes the previous 'generic bounds in type aliases are ignored' warning
2018-02-18 12:40:35 -06:00
|
Update ui test suite to use dyn
2019-05-28 13:46:13 -05:00
LL | type T1 = Box<dyn for<'xa, 'xb: 'xa> Fn(&'xa i32, &'xb i32) -> &'xa i32>;
| ^^^
Warn about more ignored bounds on type aliases
2018-02-05 14:20:57 -06:00
make bounds on higher-kinded lifetimes a hard error in ast_validation Also move the check for not having type parameters into ast_validation. I was not sure what to do with compile-fail/issue-23046.rs: The issue looks like maybe the bounds actually played a role in triggering the ICE, but that seems unlikely given that the compiler seems to entirely ignore them. However, I couldn't find a testcase without the bounds, so I figured the best I could do is to just remove the bounds and make sure at least that keeps working.
2018-03-06 04:22:24 -06:00
error: lifetime bounds cannot be used in this context
Remove licenses
2018-12-25 09:56:47 -06:00
--> $DIR/higher-lifetime-bounds.rs:65:34
Warn about more ignored bounds on type aliases
2018-02-05 14:20:57 -06:00
|
add lint to detect ignored generic bounds; this subsumes the previous 'generic bounds in type aliases are ignored' warning
2018-02-18 12:40:35 -06:00
LL | let _ : Option<for<'xa, 'xb: 'xa> fn(&'xa i32, &'xb i32) -> &'xa i32> = None;
| ^^^
Warn about more ignored bounds on type aliases
2018-02-05 14:20:57 -06:00
make bounds on higher-kinded lifetimes a hard error in ast_validation Also move the check for not having type parameters into ast_validation. I was not sure what to do with compile-fail/issue-23046.rs: The issue looks like maybe the bounds actually played a role in triggering the ICE, but that seems unlikely given that the compiler seems to entirely ignore them. However, I couldn't find a testcase without the bounds, so I figured the best I could do is to just remove the bounds and make sure at least that keeps working.
2018-03-06 04:22:24 -06:00
error: lifetime bounds cannot be used in this context
Update ui test suite to use dyn
2019-05-28 13:46:13 -05:00
--> $DIR/higher-lifetime-bounds.rs:67:42
Warn about more ignored bounds on type aliases
2018-02-05 14:20:57 -06:00
|
Update ui test suite to use dyn
2019-05-28 13:46:13 -05:00
LL | let _ : Option<Box<dyn for<'xa, 'xb: 'xa> Fn(&'xa i32, &'xb i32) -> &'xa i32>> = None;
| ^^^
Warn about more ignored bounds on type aliases
2018-02-05 14:20:57 -06:00
make bounds on higher-kinded lifetimes a hard error in ast_validation Also move the check for not having type parameters into ast_validation. I was not sure what to do with compile-fail/issue-23046.rs: The issue looks like maybe the bounds actually played a role in triggering the ICE, but that seems unlikely given that the compiler seems to entirely ignore them. However, I couldn't find a testcase without the bounds, so I figured the best I could do is to just remove the bounds and make sure at least that keeps working.
2018-03-06 04:22:24 -06:00
error: aborting due to 11 previous errors
Reference in New Issue Copy Permalink