Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Consider potential improvements for the debug.dump utility #503

Open
4 tasks
rdw-software opened this issue Feb 10, 2024 · 0 comments
Open
4 tasks

Consider potential improvements for the debug.dump utility #503

rdw-software opened this issue Feb 10, 2024 · 0 comments

Comments

@rdw-software
Copy link
Member

rdw-software commented Feb 10, 2024

It currently uses https://github.com/kikito/inspect.lua, which is... fine. But I can think of some improvements:

  • Support for cutting off the output after a (configurable) limit has been reached
  • Optional use of a colored output format so that it becomes easier to read
  • Passing in multiple return values should "just work" (e.g., dump(runtime.version()))
  • Better support for cdata (without __tostring), possibly userdata, and string buffers (hex dump?)

This is a reminder to look into if some or even all of these features are already supported by the library. Also evaluate how difficult it would be to extend the code and add those features. It's possible rewriting the dump utility might be the easiest path?

Details TBD.

# for free to join this conversation on GitHub. Already have an account? # to comment
Projects
Status: The time is nigh (Planning)
Development

No branches or pull requests

1 participant