-
Notifications
You must be signed in to change notification settings - Fork 165
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
What is the expected behaviour of BehavesAsMap? #927
Comments
@llorllale/z please, pay attention to this issue |
@victornoel which tests don't assume that |
Also note that I edited the description, I won't take care of this in #903, I already worked too much on it :) |
@victornoel you're right, the problem is in |
@victornoel can you rephrase this ticket as a bug ? |
Job #927 is now in scope, role is |
Bug was reported, see §29: +15 point(s) just awarded to @victornoel/z |
@llorllale I rewrote the description |
@victornoel Can we close it? PR was merged |
@Umbrah thanks |
@sereshqua/z please review this job completed by @umbrah/z, as in §30; the job will be fully closed and all payments will be made when the quality review is completed |
The job #927 is now out of scope |
@0crat quality good |
Quality review completed: +4 point(s) just awarded to @sereshqua/z |
Order was finished, quality is "good": +35 point(s) just awarded to @umbrah/z |
The behaviour of
BehavesAsMap
is ambiguous.If I write
new BehavesAsMap("a", "b")
, I am not expectingb
to be anything else than the value of the keya
.But many tests makes this assumption:
It should mean that
b
is indeed the value ofa
and the tests should be modified to comply with this.The text was updated successfully, but these errors were encountered: