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

tour: explain how to read a stacktrace #19422

Open
dlsniper opened this issue Mar 6, 2017 · 6 comments
Open

tour: explain how to read a stacktrace #19422

dlsniper opened this issue Mar 6, 2017 · 6 comments
Labels
Proposal-Accepted
Milestone
Unreleased

Comments

@dlsniper
Copy link
Contributor

dlsniper commented Mar 6, 2017

Hello,

I'd like to propose adding to the Tour of Go a page where the user is presented with a stack trace that occurs from a panic and guided into how to read / debug it.
I think this would be valuable for people just learning the language and would help them when they'll run for the first time into a such an issue.
If approved, I'd be happy to send a CL to do this (guidance welcomed).
What do you think?
@mvdan
Copy link
Member

mvdan commented Mar 6, 2017

Great idea. This would be especially useful for people not used to stack traces in other languages like Java or Python.

@rsc
Copy link
Contributor

rsc commented Mar 6, 2017

Great idea.

@rsc rsc added this to the Unreleased milestone Mar 6, 2017
@rsc rsc changed the title proposal: tour: explain how to read a stacktrace as part of the tour tour: explain how to read a stacktrace as part of the tour Mar 6, 2017
@rsc
Copy link
Contributor

rsc commented Mar 6, 2017

Thanks for volunteering to do this. I agree this is clearly needed.

@dlsniper dlsniper changed the title tour: explain how to read a stacktrace as part of the tour tour: explain how to read a stacktrace Mar 11, 2017
@gopherbot
Copy link

CL https://golang.org/cl/38052 mentions this issue.

@odeke-em
Copy link
Member

odeke-em commented Apr 9, 2020

@dlsniper thank you for the issue and for volunteering to work on this issue. There is some feedback on your CL from almost 2 years, please rebase and take a look if you can. Thank you.

@odeke-em
Copy link
Member

@dlsniper kindly pinging you to help send the CL instead to the x/website repository, thank you very much!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Proposal-Accepted
Projects
None yet
Milestone
Unreleased
Development

No branches or pull requests
6 participants
@rsc @dlsniper @mvdan @odeke-em @gopherbot and others