Make json output more informative for functions. #6380
Conversation
It now includes the attributes I was able to find as well as the return type, linkage, and purity.
This explicitly includes the return type because a function might be declared without an explicit
return type (eg `int i; auto ref foo() { return i; }`) and that results in a type in the json of
`ref ()`.
| property("parameters", tf.parameters); | ||
| property("trust", tf.trust); | ||
| propertyBool("nothrow", tf.isnothrow); | ||
| propertyBool("nogc", tf.isnogc); |
There was a problem hiding this comment.
It might be worthwhile to put these under attributes, especially considering that UDAs should also be part of the output.
|
@dhasenan Are you still interested in pursuing this? |
Using protocol buffers (eg https://github.com/msoucy/dproto) would reduce need for such hacks, and have many other advantages, primarily type/schema safety, better performance, ease of reading and writing. |
|
@dhasenan why did you close this? |
|
Because I am not currently able to spend any time on it. It's over a year old and probably has merge errors. |
|
No problem. I'll see if someone else wants to pick it up. |
WalterBright
added
the
Phantom Zone
It now includes the attributes I was able to find as well as the return type, linkage, and purity.
This explicitly includes the return type because a function might be declared without an explicit
return type (eg
int i; auto ref foo() { return i; }) and that results in a type in the json ofref ().