-
Notifications
You must be signed in to change notification settings - Fork 111
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
Revising the addition of a docstring #583
Comments
Should work? 200 lines of tests say so! Lines 1055 to 1269 in 1dd0a70
Which of course just means that there is some other error or circumstances that are missing tests. |
Interesting. Here's what I was trying (Julia 1.5.0, Revise 3.1.9) module TestPackage
greet(name="World") = "Hello $(name), nice to meet you!"
end # module
Edit the module to contain: module TestPackage
"""
greet
foo
"""
greet(name="World") = "Hello to $(name), so glad to see you!"
end # module then:
|
Ah, it works if it already has a docstring — it's the adding of a new docstring that doesn't. |
Color me amazed. Despite trying to set up good APIs and sensible logic, I get caught over and over again by subtle differences blocking something that should work. It seems that almost every single thing anyone ever wants to do needs a test. |
I just need to do more live and interactive demos. They have a way of exploring new paths in fun and exciting ways! |
You are so right. I notice everything bad about Julia whenever I'm teaching someone new or demonstrating how awesome it is. 😆 |
It also requires that the module have no docstrings whatsoever. It's a Julia bug. Fix coming momentarily. |
Workaround for julia#38819 Fixes #583
xref JuliaLang/julia#38819 and fix in 38821. |
Workaround for julia#38819 Fixes #583
Fixes #38819 Fixes timholy/Revise.jl#583 (cherry picked from commit ab35e37)
Ok, this is a little silly, but I was just demoing Revise to someone and blindly tried adding a docstring, expecting it to become available (akin to other changes).
Not a crucial thing, but could be nice to support.
The text was updated successfully, but these errors were encountered: