12dc24f460
This commit is a response to feedback on the displayed type signatures results, by making generics act stricter. Generics are tightened by making order significant. This means `Vec<Allocator>` now matches only with a true vector of allocators, instead of matching the second type param. It also makes unboxing within generics stricter, so `Result<A, B>` only matches if `B` is in the error type and `A` is in the success type. The top level of the function search is unaffected. Find the discussion on: * <https://rust-lang.zulipchat.com/#narrow/stream/393423-t-rustdoc.2Fmeetings/topic/meeting.202024-07-08/near/449965149> * <https://github.com/rust-lang/rust/pull/124544#issuecomment-2204272265> * <https://rust-lang.zulipchat.com/#narrow/channel/266220-t-rustdoc/topic/deciding.20on.20semantics.20of.20generics.20in.20rustdoc.20search/near/476841363>
40 lines
1.2 KiB
JavaScript
40 lines
1.2 KiB
JavaScript
// exact-check
|
|
|
|
const EXPECTED = [
|
|
// Trait-associated types (that is, associated types with no constraints)
|
|
// are treated like type parameters, so that you can "pattern match"
|
|
// them. We should avoid redundant output (no `Item=MyIter::Item` stuff)
|
|
// and should give reasonable results
|
|
{
|
|
'query': 'MyIter<T> -> Option<T>',
|
|
'correction': null,
|
|
'others': [
|
|
{
|
|
'path': 'assoc_type_unbound::MyIter',
|
|
'name': 'next',
|
|
'displayType': '&mut `MyIter` -> `Option`<`MyIter::Item`>',
|
|
'displayMappedNames': 'T = MyIter::Item',
|
|
'displayWhereClause': '',
|
|
},
|
|
],
|
|
},
|
|
{
|
|
'query': 'MyIter<Item=T> -> Option<T>',
|
|
'correction': null,
|
|
'others': [
|
|
{
|
|
'path': 'assoc_type_unbound::MyIter',
|
|
'name': 'next',
|
|
'displayType': '&mut `MyIter` -> `Option`<`MyIter::Item`>',
|
|
'displayMappedNames': 'T = MyIter::Item',
|
|
'displayWhereClause': '',
|
|
},
|
|
],
|
|
},
|
|
{
|
|
'query': 'MyIter<T> -> Option<Item=T>',
|
|
'correction': null,
|
|
'others': [],
|
|
},
|
|
];
|