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.

Sign up for GitHub

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

Jump to bottom

Call stack traces for arbitrary types #158

Open
fmease opened this issue Aug 4, 2022 · 0 comments
Open

Call stack traces for arbitrary types #158

fmease opened this issue Aug 4, 2022 · 0 comments
Labels
design Open design questions that need to be solved T-enhancement Type: Enhancement

Comments

@fmease
Copy link
Owner

fmease commented Aug 4, 2022 •
edited
Loading

Meta: Task: Add description, motivation etc.

Initial implementation should focus on core.option.Option and core.result.Result if that's easier to work with.
(Design work is necessary around how to design the CLI / etc. for it to take a type as an argument; a fully qualified path is not necessarily unique e.g. with packages that share their name).

Keyword: Instrumentation.

Both static (compile time) and dynamic (run time) traces should be supported.

Mock up:

Meta: Task
@fmease fmease added design Open design questions that need to be solved T-enhancement Type: Enhancement labels Aug 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
design Open design questions that need to be solved T-enhancement Type: Enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@fmease