bpo-41513: Make steps after the loop consistent with the loop body#22315
Merged
rhettinger merged 1 commit intopython:masterfrom Sep 19, 2020
Merged
bpo-41513: Make steps after the loop consistent with the loop body#22315rhettinger merged 1 commit intopython:masterfrom
rhettinger merged 1 commit intopython:masterfrom
Conversation
rhettinger
changed the title
xzy3
pushed a commit
to xzy3/cpython
that referenced
this pull request
Oct 18, 2020
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Make the post-loop code more consistent with the loop body. Improves internal accuracy by not prematurely combining the separate accumulators.
Accuracy measurements. "hypot3" is current baseline. "hypot12" includes this PR. Column 1 is the number of dimensions. Column 2 is the weighted average number of bits of accuracy (higher is better). Column 3 is the algorithm. Column 4 has counts for number of bits of accuracy,
(104, 111)means 111 cases where the accuracy was 104 bits:https://bugs.python.org/issue41513