-
Notifications
You must be signed in to change notification settings - Fork 12
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
Make using DeclareGlobalName
for functions work
#258
Comments
Unfortunately I guess we could/should add a way to indicate the type... In the meantime you could just use DeclareGlobalVariable/Function |
Could we add logic into AutoDoc that if a global variable gets an And in the meantime I'll use |
In theory: sure, I'd be happy to merge such a change. In practice, someone has to figure out how to do it ;-) |
Is this something we could let one of the student assistants do? Not now but in a few months, say. I have no idea how AutoDoc works internally, so I really don't know. |
That depends on them; also on how much GAP they'll pick up. But diving into a new unfamiliar codebase is always challenging. Anyway, I could so it in principle, but my time is limited (time I was able to fully dedicate to work today so far: 0. At least I could type some issue replies or emails on my phone... |
Relevant place in the code: Line 111 in f47e3fd
@Arguments to "convert" the node types as needed
|
Let me also point out that in general, it would be good if one could attach a AutoDoc comment to a function declared via Because in many cases I think it is by far preferable to directly attach a doc comment to the implementation, not some otherwise useless "declaration". |
When I use
DeclareGlobalName
together with an@Description
comment, then I get this, and I can't use the@Arguments
comment:Edit: I think adding an
@Arguments
comment should make AutoDoc handle the variable in question as a function instead of as a global variable.The text was updated successfully, but these errors were encountered: