You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As mentioned in the original typedsignatures issue: #20 (comment)
generic julia code often doesn't have a definite return type. Would it be possible to either customize TYPEDSIGNATURES to omit this (or create a new behavior) to show input type annotations while omitting any inferred output types? As it is, I have very many f(x) -> Any signatures in my documentation, which is misleading since they are actually type stable.
The text was updated successfully, but these errors were encountered:
Yes, that's probably doable. It would need to have a similar approach to https://github.com/JuliaDocs/DocStringExtensions.jl/blob/master/src/abbreviations.jl#L43 where the abbreviation type gets a field that can be used to set whether it shows the return type or not. I'm happy to guide the implementation but don't really have the bandwidth to implement it in the short-term myself.
tomerarnon
changed the title
TYPEDSIGNATURES without output type
Feature request: TYPEDSIGNATURES without output type
Oct 5, 2023
As mentioned in the original typedsignatures issue: #20 (comment)
generic julia code often doesn't have a definite return type. Would it be possible to either customize
TYPEDSIGNATURES
to omit this (or create a new behavior) to show input type annotations while omitting any inferred output types? As it is, I have very manyf(x) -> Any
signatures in my documentation, which is misleading since they are actually type stable.The text was updated successfully, but these errors were encountered: