Tomas Fiers
Tomas Fiers
Yeah no. Has no default values eg (and would be super difficult, code_lowered and shi: https://github.com/JuliaDocs/DocStringExtensions.jl/issues/107#issuecomment-928926677) A way: @macro for whole module. `Meta.@dump function f(a, b=3; c=8); (a,b,c) end` and...
Is it an idea to wrap `@doc` instead? Then you'd have to do it below def: ``` function blah(x, y=3) … end @mydoc blah """ Yeetus """ ``` eh
Aha: we'd use `@code_string`, https://github.com/timholy/CodeTracking.jl#code_string-and-code_expr
how does julia-vscode do it btw?
Concrete motivation: I was weighing whether to add LiveServer to docs/Project.toml (or alternatively to just have it in global v1.8 env) and I see it introduced quite some new deps...
> I was weighing whether to add LiveServer to docs/Project.toml (or alternatively to just have it in global v1.8 env) (btw in the end I went with a secret, third...
So concrete idea: - for installed in current project only - t0; eval using $module; t1 Just go down list (or up list rather. 'topological sort')? And done. Add to...
Do we then have multiple roots, or still one (that's then the pkg name, or the project name == dirname (always?))
[This should probably go in docs or readme]
Especially useful when in the dev dir of a project (the package is then "not found" in manifest)