Skip to content
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

Support multiple return values #7485

Open
astrelsky opened this issue Feb 12, 2025 · 2 comments
Open

Support multiple return values #7485

astrelsky opened this issue Feb 12, 2025 · 2 comments
Assignees
Labels
Status: Prioritize This is currently being prioritized

Comments

@astrelsky
Copy link
Contributor

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.

@ryanmkurtz
Copy link
Collaborator

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.

@astrelsky
Copy link
Contributor Author

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.

@ryanmkurtz ryanmkurtz self-assigned this Feb 14, 2025
@ryanmkurtz ryanmkurtz added the Status: Prioritize This is currently being prioritized label Feb 14, 2025
@ryanmkurtz ryanmkurtz assigned caheckman and unassigned ryanmkurtz Feb 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Prioritize This is currently being prioritized
Projects
None yet
Development

No branches or pull requests

3 participants