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
Is your feature request related to a problem? Please describe.
I'm always frustrated when I'm reversing something written in a programming language that supports multiple return values and I have to spend hours manually creating structures every time I encounter one.
Describe the solution you'd like
Support multiple return values when editing a function signature.
Describe alternatives you've considered
Continue to waste time manually creating them when necessary. It is very tedious and isn't scriptable.
The text was updated successfully, but these errors were encountered:
I ran into this with the Swift Demangler. I had to make a ton of tuple structs to simulate it, which resulted in a ton of conflicting data types.
You can do what was done for go and tie the return type to the function by including the function name in the type. That will avoid conflicts but also creates a ton of bloat and only works for something automated. If there is no metadata to use for analysis and it needs to be done manually, it's not a good time.
Is your feature request related to a problem? Please describe.
I'm always frustrated when I'm reversing something written in a programming language that supports multiple return values and I have to spend hours manually creating structures every time I encounter one.
Describe the solution you'd like
Support multiple return values when editing a function signature.
Describe alternatives you've considered
Continue to waste time manually creating them when necessary. It is very tedious and isn't scriptable.
The text was updated successfully, but these errors were encountered: