[Issue 17650] [REG v2.075.0 b1-b4] std.getopt range violation

2018-01-05 Thread d-bugmail--- via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=17650 --- Comment #14 from github-bugzi...@puremagic.com --- Commits pushed to dmd-cxx at https://github.com/dlang/phobos https://github.com/dlang/phobos/commit/296184f5419e1a7f8748688606950e747338f8f1 Fix issue 17650: std.getopt range violation when

[Issue 17650] [REG v2.075.0 b1-b4] std.getopt range violation

2017-08-16 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=17650 --- Comment #13 from github-bugzi...@puremagic.com --- Commits pushed to stable at https://github.com/dlang/phobos https://github.com/dlang/phobos/commit/296184f5419e1a7f8748688606950e747338f8f1 Fix issue 17650: std.getopt range violation when

[Issue 17650] [REG v2.075.0 b1-b4] std.getopt range violation

2017-07-19 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=17650 --- Comment #12 from github-bugzi...@puremagic.com --- Commit pushed to master at https://github.com/dlang/phobos https://github.com/dlang/phobos/commit/7a0ff521f296fef66455a84f11864b9cb046c43a Fix issue 17650: std.getopt range violation when option

[Issue 17650] [REG v2.075.0 b1-b4] std.getopt range violation

2017-07-15 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=17650 --- Comment #11 from github-bugzi...@puremagic.com --- Commit pushed to stable at https://github.com/dlang/phobos https://github.com/dlang/phobos/commit/7a0ff521f296fef66455a84f11864b9cb046c43a Fix issue 17650: std.getopt range violation when option

[Issue 17650] [REG v2.075.0 b1-b4] std.getopt range violation

2017-07-15 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=17650 --- Comment #10 from github-bugzi...@puremagic.com --- Commits pushed to master at https://github.com/dlang/phobos https://github.com/dlang/phobos/commit/296184f5419e1a7f8748688606950e747338f8f1 Fix issue 17650: std.getopt range violation when

[Issue 17650] [REG v2.075.0 b1-b4] std.getopt range violation

2017-07-15 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=17650 github-bugzi...@puremagic.com changed: What|Removed |Added Status|NEW |RESOLVED

[Issue 17650] [REG v2.075.0 b1-b4] std.getopt range violation

2017-07-15 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=17650 --- Comment #9 from Jon Degenhardt --- https://github.com/dlang/phobos/pull/5612 --

[Issue 17650] [REG v2.075.0 b1-b4] std.getopt range violation

2017-07-15 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=17650 --- Comment #8 from Jon Degenhardt --- I'm preparing a PR to fix the underlying issue. A concern for the general release is that a single hyphen is often used to represent standard input in command line args. e.g. $

[Issue 17650] [REG v2.075.0 b1-b4] std.getopt range violation

2017-07-15 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=17650 --- Comment #7 from Jon Degenhardt --- (In reply to ZombineDev from comment #6) > The error doesn't make sense to me. @safe adds bounds checks where there are > none only when building with -release. I.e. if we're not

[Issue 17650] [REG v2.075.0 b1-b4] std.getopt range violation

2017-07-15 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=17650 ZombineDev changed: What|Removed |Added CC|

[Issue 17650] [REG v2.075.0 b1-b4] std.getopt range violation

2017-07-15 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=17650 --- Comment #5 from Jon Degenhardt --- Wow. So I introduced this, initiated by trying add new unit tests. And my own unit tests caught it, but unfortunately, not the unit tests I added to Phobos. How ironic. Thanks for

[Issue 17650] [REG v2.075.0 b1-b4] std.getopt range violation

2017-07-14 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=17650 --- Comment #4 from Vladimir Panteleev --- Actually, I believe we do count a breakage as a regression if something breaks for the end-user, regardless of what is going on under the hood. E.g. it's possible that for

[Issue 17650] [REG v2.075.0 b1-b4] std.getopt range violation

2017-07-14 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=17650 --- Comment #3 from Vladimir Panteleev --- Interesting - looking at the PR, this doesn't really seem like a regression, rather that the addition of the @safe attribute exposed an out-of-bounds array access that was

[Issue 17650] [REG v2.075.0 b1-b4] std.getopt range violation

2017-07-14 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=17650 --- Comment #2 from Vladimir Panteleev --- Introduced in https://github.com/dlang/phobos/pull/5351 --

[Issue 17650] [REG v2.075.0 b1-b4] std.getopt range violation

2017-07-14 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=17650 Martin Nowak changed: What|Removed |Added CC||c...@dawg.eu --- Comment #1

[Issue 17650] [REG v2.075.0 b1-b4] std.getopt range violation

2017-07-14 Thread via Digitalmars-d-bugs
https://issues.dlang.org/show_bug.cgi?id=17650 Jon Degenhardt changed: What|Removed |Added Severity|enhancement |regression