[Bug]: Unstable iterator overloads always warn, even if another overload is used #26590
Comments
|
Note that I've only written a test for the serial case, but this was happening for standalone, leader, and follower iterators as well. Tests should be added for those before considering this issue resolved |
lydia-duncan
added a commit
that referenced
this issue
Jan 23, 2025
…6591) [reviewed by @benharsh because I lacked confidence, thanks!] See #26590 . Basically, marking any iterator as unstable will cause the unstable warning to fire, even if that particular iterator is not used. This test demonstrates the issue for serial iterators, but standalone, leader, and follower iterators were also exhibiting the same behavior (and I suspect will be solved by the same solution).
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary of Problem
Description:
In fixing a bug with set's iterators, I discovered that marking any overload of an iterator as unstable will cause it to fire every time that iterator is referred to, even if ultimately the iterator used was not the unstable one.
Is this issue currently blocking your progress?
No, though it is encouraging me to only mark one of the iterators as unstable instead of all of them, since it'll trigger for all cases anyways.
Steps to Reproduce
Source Code:
A test demonstrating the issue is a little too complicated to put here, so I'll just link to the future I'm filing
Compile command:
chpl foo.chpl --warn-unstableExecution command:
N/A
Associated Future Test(s):
test/unstable-keyword/iterator/onlySerial.chpl#26591Configuration Information
chpl --version: 2.4.0 pre-release$CHPL_HOME/util/printchplenv --anonymize: anygcc --versionorclang --version: anymodule list: N/AThe text was updated successfully, but these errors were encountered: