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
While the docs outline the most basic usage, I was trying to put the try-except for the call to parse inside a proc and return the result... but have no not been able to do better than return a ref untyped.
I see an issue referring to an OptsArgparse type when I used the wrong type, but OptsArgparse isn't defined either.
Could you provide guidance (and ideally docs) on what the return of parse is?
The text was updated successfully, but these errors were encountered:
jmetz
changed the title
Add docs explaining how to use output of parse
Add docs descriing output type of parse
Jan 22, 2021
jmetz
changed the title
Add docs descriing output type of parse
Add docs describing output type of parse
Jan 22, 2021
@jmetz at this point, ref untyped is likely the best you can do. I've been annoyed by this limitation a few times, too.
I almost succeeded in getting argparse to generate a consistent type name for the data returned by parse but was prevented by this bug: nim-lang/Nim#16118 I'll see if it's still an issue in the latest Nim.
While the docs outline the most basic usage, I was trying to put the try-except for the call to
parse
inside a proc and return the result... but have no not been able to do better than return aref untyped
.I see an issue referring to an
OptsArgparse
type when I used the wrong type, butOptsArgparse
isn't defined either.Could you provide guidance (and ideally docs) on what the return of
parse
is?The text was updated successfully, but these errors were encountered: