Closed thofma closed 5 years ago
Looking at the documentation again (https://docs.julialang.org/en/v1/manual/documentation/index.html), I read that "Note that no blank lines or comments may intervene between a docstring and the documented object.".
So at the end, this is not a bug in Revise/JuliaInterpreter?
Right, watch what happens at the REPL:
julia> """
bla
"""
# s
"bla\n"
julia> function f()
return 1
end
f (generic function with 1 method)
help?> f
search: f fd for fma fld fld1 fill fdio frexp foldr foldl flush floor float first fill! fetch fldmod filter falses finally foreach fldmod1 findmin findmax findall filter!
No documentation found.
f is a Function.
# 1 method for generic function "f":
[1] f() in Main at REPL[2]:2
The same is true if you put it in a file. Finally, using @doc
explicitly is rarely necessary anymore.
But many thanks for the report about empty files! Fix coming.
I think you may have to reopen it (https://github.com/JuliaLang/julia/issues/31470#issuecomment-476368692). Or should I open a new issue over at JuliaDebugger?
Thanks!
Thanks again for your amazing work @timholy. After updating to
v2.0.1
, I noticed the following regression: Revise now refuses/fails to track a file if there is a comment between a docstring and a function definition, like in:The error is:
P.S. It also chokes on empty files.