-
-
Notifications
You must be signed in to change notification settings - Fork 11
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
Adopt Base's annotated types/functions as API #81
Conversation
This change has been discussed with other maintainers on Slack (the API shift, but not the exporting), so I'm inclined to merge this soon if I can figure out how to make doctests happy. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me, thanks @tecosaur
d1d62bc
to
1beedda
Compare
This is held up by difficulty figuring out the Documenter side of things. |
It's hard to see how I can make this work before JuliaDocs/Documenter.jl#1781 is resolved 😬. Perhaps @mortenpi might have an idea? |
1beedda
to
769e49a
Compare
8264fc8
to
0e3281a
Compare
In light of JuliaLang/julia#55845 and the change Kristoffer's just pushed it seems like neither of us can easily make Documenter do what we want here, so let's just leave the documentation of the Base-defined types there with an appropriate notice. I think all that needs to be done now is the |
This opens the door to shuffling parts currently implemented in Base into this stdlib without breaking any public APIs. It would be nice to actually show the relevant Annotated* docstrings, but unfortunately due to JuliaDocs/Documenter.jl#1781 it's a bit difficult to actually do so. We should re-visit this later.
ba8ec41
to
d9d7472
Compare
I don't think there's anything else that needs changing? |
This opens the door to shuffling parts currently implemented in Base into this stdlib without breaking any public APIs.
To try to help avoid people using
Base.Annot...
anyway, I've exported these bindings. I think this is reasonable given unlike inBase
this library needs to be deliberately imported.