-
Notifications
You must be signed in to change notification settings - Fork 80
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Warn about accessing private members in documented unittest
s
#893
Comments
Actually, I'll add one condition: If the documented unittest is for a private symbol, no warning should be emitted. |
If you like this, it can be extended to |
I would not extend it to protected. Remember we want to minimize the amount of boilerplate here. |
This was suggested to me by @Geod24 in https://issues.dlang.org/show_bug.cgi?id=21462
A unit test should not be accessing
private
members when it is documented; the same sequence of instructions won’t compile for a user of the module. If the documentation comment for the unit test starts withPrivate.
(case insensitive) or isditto
and the referred documentation starts withPrivate.
, the warning is suppressed.The text was updated successfully, but these errors were encountered: