Adjustment on the value extractor resolution algorithm for "non-generic containers"

Description

So first, this paragraph was rebranded for "non-generic containers" whereas it indeed also concerns this case:

as the first paragraph states it.

We agreed on discouraging this but it looks like this paragraph is also about it.

Another point is that in the RI, we also throw an exception in this case:

even if we have only one VE defined for the key and no VE defined for the value.

2 things here:

  • not sure throwing an exception is the best we can do

  • if we consider we should throw an exception, then we should take this case into account in the resolution algorithm

Environment

None

Activity

Show:
Gunnar Morling
June 21, 2017, 3:09 PM

, I'll change the section title.

On your second question, the RI seems to violate the spec here. It says

If the constraint carries the Unwrapping.Unwrap payload and there is exactly one maximally-specific type-compliant value extractor, this extractor is applied

So the exception seems not justified. Can you file an HV issue?

Assignee

Gunnar Morling

Reporter

Guillaume Smet

Labels

None

Feedback Requested

None

Feedback Requested By

None

backPortable

None

Suitable for new contributors

None

backportDecision

None

backportReEvaluate

None

Components

Fix versions

Priority

Major
Configure