[Feature Request] Improve stacktrace readability (with line numbers)
Open
enhancement
- Dominant language
- Rust
- Stars
- 378
- Forks
- 137
- PR merge metrics
- No merged PRs in 30d
Description
Today if we call `Debug::print_stack_trace`, it prints a stack with very low-level data: bytecode, stack information and etc.
This however isn't typically what a Move developer wants.
The basic thing a developer want to see would be the similar kind of stacktrace in other languages: the file and line number of each function in the stack.
Contributor guide
Assessment
This issue has not been assessed yet.