diff options
| author | Sebastian Berg <sebastian@sipsolutions.net> | 2020-06-16 16:34:58 -0500 |
|---|---|---|
| committer | Sebastian Berg <sebastian@sipsolutions.net> | 2020-06-16 20:48:44 -0500 |
| commit | 1fab43749913aaa63168e4fdaaefffa67e9da36f (patch) | |
| tree | 96d6783f8c8897d3621e4c1c2392240f9d6ff23c /numpy/polynomial/polyutils.py | |
| parent | 1fb7047b0ceba98d43b50ebb398be899ff8f6a1c (diff) | |
| download | numpy-1fab43749913aaa63168e4fdaaefffa67e9da36f.tar.gz | |
BUG: Initialize stop-reading in array_from_text
This should probably be hit with count=0, which is why added
a test which takes that path. However, I was not actually
able to trigger any issue (not even a warning in valgrind).
I assume that since this is on the stack, its just hard to
trigger.
This came up in another CI-run. I suppose gcc as well as clang seem
to notice that it can be used uninitialized (which is true).
Diffstat (limited to 'numpy/polynomial/polyutils.py')
0 files changed, 0 insertions, 0 deletions