-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Make hasdoc
public
#52708
Make hasdoc
public
#52708
Conversation
Should it simply be exported? (Note that even if you add |
Now exporting |
s/exported/public/
I also fixed the docstring to refer to "public" symbols rather than "exported" symbols, following #52413 (comment) by @LilithHafner |
I don't see much advantage of exporting from a submodule (historically, I'm guessing the primary uses were to mark the symbols public and when a symbol was previously defined in Base and moved to a submodule) |
In favor of
|
If we are going to export |
Bump. |
The declared semantics of c.f. #52413 (comment) The original commit (make hasdoc public) is definitely mergable, though. |
@LilithHafner, (This PR just needs to be updated merge the latest |
Clearly not, lol. You are quite right. |
Making
Docs.hasdoc
public
per @LilithHafner #52139 (comment).