nordic-dev.net/rust
nordic-dev.net/rust
2
0
Fork 0
mirror of https://github.com/rust-lang/rust.git synced 2024-11-22 23:04:33 +00:00
Code Issues Packages Projects Releases Wiki Activity
14b96659e4
rust/src/test/ui/higher-lifetime-bounds.stderr

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 10:22:24 +00:00
error: lifetime bounds cannot be used in this context
Split param-bounds-ignored into two, it was testing two independent things Also, tweak the test for ignored type aliases such that replacing the type alias by a newtype struct leads to a well-formed type definition, and errors when used the way the type alias is used.
2018-03-10 10:22:55 +00:00
--> $DIR/higher-lifetime-bounds.rs:18:22
Warn about more ignored bounds on type aliases
2018-02-05 20:20:57 +00: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 10:22:24 +00: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 18:40:35 +00: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 10:22:24 +00:00
error: lifetime bounds cannot be used in this context
Split param-bounds-ignored into two, it was testing two independent things Also, tweak the test for ignored type aliases such that replacing the type alias by a newtype struct leads to a well-formed type definition, and errors when used the way the type alias is used.
2018-03-10 10:22:55 +00:00
--> $DIR/higher-lifetime-bounds.rs:26:34
add lint to detect ignored generic bounds; this subsumes the previous 'generic bounds in type aliases are ignored' warning
2018-02-18 18:40:35 +00: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 10:22:24 +00:00
error: lifetime bounds cannot be used in this context
Split param-bounds-ignored into two, it was testing two independent things Also, tweak the test for ignored type aliases such that replacing the type alias by a newtype struct leads to a well-formed type definition, and errors when used the way the type alias is used.
2018-03-10 10:22:55 +00:00
--> $DIR/higher-lifetime-bounds.rs:41:28
add lint to detect ignored generic bounds; this subsumes the previous 'generic bounds in type aliases are ignored' warning
2018-02-18 18:40:35 +00: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 10:22:24 +00:00
error: lifetime bounds cannot be used in this context
Split param-bounds-ignored into two, it was testing two independent things Also, tweak the test for ignored type aliases such that replacing the type alias by a newtype struct leads to a well-formed type definition, and errors when used the way the type alias is used.
2018-03-10 10:22:55 +00:00
--> $DIR/higher-lifetime-bounds.rs:53:25
add lint to detect ignored generic bounds; this subsumes the previous 'generic bounds in type aliases are ignored' warning
2018-02-18 18:40:35 +00: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 10:22:24 +00:00
error: lifetime bounds cannot be used in this context
Split param-bounds-ignored into two, it was testing two independent things Also, tweak the test for ignored type aliases such that replacing the type alias by a newtype struct leads to a well-formed type definition, and errors when used the way the type alias is used.
2018-03-10 10:22:55 +00:00
--> $DIR/higher-lifetime-bounds.rs:61:28
add lint to detect ignored generic bounds; this subsumes the previous 'generic bounds in type aliases are ignored' warning
2018-02-18 18:40:35 +00: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 10:22:24 +00:00
error: lifetime bounds cannot be used in this context
Split param-bounds-ignored into two, it was testing two independent things Also, tweak the test for ignored type aliases such that replacing the type alias by a newtype struct leads to a well-formed type definition, and errors when used the way the type alias is used.
2018-03-10 10:22:55 +00:00
--> $DIR/higher-lifetime-bounds.rs:63:40
add lint to detect ignored generic bounds; this subsumes the previous 'generic bounds in type aliases are ignored' warning
2018-02-18 18:40:35 +00: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 10:22:24 +00:00
error: lifetime bounds cannot be used in this context
Split param-bounds-ignored into two, it was testing two independent things Also, tweak the test for ignored type aliases such that replacing the type alias by a newtype struct leads to a well-formed type definition, and errors when used the way the type alias is used.
2018-03-10 10:22:55 +00:00
--> $DIR/higher-lifetime-bounds.rs:65:37
add lint to detect ignored generic bounds; this subsumes the previous 'generic bounds in type aliases are ignored' warning
2018-02-18 18:40:35 +00: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 10:22:24 +00:00
error: lifetime bounds cannot be used in this context
Split param-bounds-ignored into two, it was testing two independent things Also, tweak the test for ignored type aliases such that replacing the type alias by a newtype struct leads to a well-formed type definition, and errors when used the way the type alias is used.
2018-03-10 10:22:55 +00:00
--> $DIR/higher-lifetime-bounds.rs:68:29
add lint to detect ignored generic bounds; this subsumes the previous 'generic bounds in type aliases are ignored' warning
2018-02-18 18:40:35 +00: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 10:22:24 +00:00
error: lifetime bounds cannot be used in this context
Split param-bounds-ignored into two, it was testing two independent things Also, tweak the test for ignored type aliases such that replacing the type alias by a newtype struct leads to a well-formed type definition, and errors when used the way the type alias is used.
2018-03-10 10:22:55 +00:00
--> $DIR/higher-lifetime-bounds.rs:71:29
add lint to detect ignored generic bounds; this subsumes the previous 'generic bounds in type aliases are ignored' warning
2018-02-18 18:40:35 +00:00
|
LL | type T1 = Box<for<'xa, 'xb: 'xa> Fn(&'xa i32, &'xb i32) -> &'xa i32>;
| ^^^
Warn about more ignored bounds on type aliases
2018-02-05 20:20:57 +00: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 10:22:24 +00:00
error: lifetime bounds cannot be used in this context
Split param-bounds-ignored into two, it was testing two independent things Also, tweak the test for ignored type aliases such that replacing the type alias by a newtype struct leads to a well-formed type definition, and errors when used the way the type alias is used.
2018-03-10 10:22:55 +00:00
--> $DIR/higher-lifetime-bounds.rs:75:34
Warn about more ignored bounds on type aliases
2018-02-05 20:20:57 +00:00
|
add lint to detect ignored generic bounds; this subsumes the previous 'generic bounds in type aliases are ignored' warning
2018-02-18 18:40:35 +00: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 20:20:57 +00: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 10:22:24 +00:00
error: lifetime bounds cannot be used in this context
Split param-bounds-ignored into two, it was testing two independent things Also, tweak the test for ignored type aliases such that replacing the type alias by a newtype struct leads to a well-formed type definition, and errors when used the way the type alias is used.
2018-03-10 10:22:55 +00:00
--> $DIR/higher-lifetime-bounds.rs:77:38
Warn about more ignored bounds on type aliases
2018-02-05 20:20:57 +00:00
|
add lint to detect ignored generic bounds; this subsumes the previous 'generic bounds in type aliases are ignored' warning
2018-02-18 18:40:35 +00:00
LL | let _ : Option<Box<for<'xa, 'xb: 'xa> Fn(&'xa i32, &'xb i32) -> &'xa i32>> = None;
| ^^^
Warn about more ignored bounds on type aliases
2018-02-05 20:20:57 +00: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 10:22:24 +00:00
error: aborting due to 11 previous errors
Reference in New Issue Copy Permalink