subject:"\[Issue 18623\] Documented unittest should not allow private symbol access"

[Issue 18623] Documented unittest should not allow private symbol access

2022-03-10 Thread d-bugmail--- via Digitalmars-d-bugs

https://issues.dlang.org/show_bug.cgi?id=18623 --- Comment #9 from Nick Treleaven --- >From the pull: > If someone wants to document private symbols, why prevent it ? > In the example, the documented unittest is attached to a private symbol, > isn't it ? If you want to support that unusual ca

[Issue 18623] Documented unittest should not allow private symbol access

2022-03-10 Thread d-bugmail--- via Digitalmars-d-bugs

https://issues.dlang.org/show_bug.cgi?id=18623 RazvanN changed: What|Removed |Added Status|NEW |RESOLVED CC|

[Issue 18623] Documented unittest should not allow private symbol access

2022-03-08 Thread d-bugmail--- via Digitalmars-d-bugs

--- @RazvanN7 created dlang/dmd pull request #13783 "Fix Issue 18623 - Documented unittest should not allow private symbol access" fixing this issue: - Fix Issue 18623 - Documented unittest should not allow private symbol access https://github.com/dlang/dmd/pull/13783 --

[Issue 18623] Documented unittest should not allow private symbol access

2018-07-02 Thread d-bugmail--- via Digitalmars-d-bugs

https://issues.dlang.org/show_bug.cgi?id=18623 --- Comment #6 from greenify --- FWIW the tools extractor that is used by Phobos is now on dub: https://code.dlang.org/packages/dtools dub fetch dtools dub run dtools:tests_extractor --

[Issue 18623] Documented unittest should not allow private symbol access

2018-05-06 Thread d-bugmail--- via Digitalmars-d-bugs

https://issues.dlang.org/show_bug.cgi?id=18623 --- Comment #5 from greenify --- Andrei and Walter are not really keen on adding more and more cli switches. The unittest extraction pipeline is far from ideal, but it's probably the best we will get in this sector. --

[Issue 18623] Documented unittest should not allow private symbol access

2018-05-06 Thread d-bugmail--- via Digitalmars-d-bugs

https://issues.dlang.org/show_bug.cgi?id=18623 --- Comment #4 from Steven Schveighoffer --- I agree that can be a valid concern. Let me restate that I would recommend if we do this, make it an opt-in switch. --

[Issue 18623] Documented unittest should not allow private symbol access

2018-05-05 Thread d-bugmail--- via Digitalmars-d-bugs

https://issues.dlang.org/show_bug.cgi?id=18623 --- Comment #3 from Nick Treleaven --- (In reply to Steven Schveighoffer from comment #2) > You may want to test things inside > your unit test that have nothing to do with the example, but use the same > code for setup, and then you have to write th