-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
1.10/master regression on Dict/Set #51594
Comments
Looks like Line 258 in 165f728
|
So it seems that 86b819c, which added the assertion, is probably the commit that triggers it. |
As pointed out in #51594 (comment), this is necessary for the assertion added in #49447 to be valid.
fixed by #51595 |
Something else very odd is happening here. Ok. so the cause is that |
|
so the problem is that it's only testing merging dicts of equal sizes, and ignoring the possibility that the dict already has a user chosen sizehint. I think we should change the logic to only sizehint if the anticipated length after the merge is larger than the capacity*load_factor of the dict we're merging into |
The following code triggers the "never trigger" assertion reliably.
This reproduces on the Linux aarch64 binary for the 1.10 beta and also nightly but not on 1.9.3. It also reproduces on the Linux x86_64 nightly binary. From old versions I have around this does not happen on 4c32381 but does happen on 21d4c2f. I have not tried to reduce/debug/bisect this further yet.
Reduced test case:
The text was updated successfully, but these errors were encountered: