Skip to content

runtime: distinguish throw vs. panic in new go runtime code #8380

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
Closed
randall77 opened this issue Jul 17, 2014 · 2 comments
Closed

runtime: distinguish throw vs. panic in new go runtime code #8380

randall77 opened this issue Jul 17, 2014 · 2 comments
Labels
FrozenDueToAge

Comments

@randall77
Copy link
Contributor 

Expose runtime.throw to runtime and use it instead of panic where we don't want a
failure to be catchable.

Use it in hashmap.go, probably other places.
@gopherbot
Copy link
Contributor

Comment 1:

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

@davecheney
Copy link
Contributor

Comment 2:

This issue was closed by revision ec5d7ba.

Status changed to Fixed.

@golang golang locked and limited conversation to collaborators Jun 25, 2016
wheatman pushed a commit to wheatman/go-akaros that referenced this issue Jun 25, 2018
@davecheney @wheatman
runtime: add throwgo
8c0d1ca 
Fixes golang#8380.

Also update hashmap.go to use throwgo rather than panic.

LGTM=khr
R=khr, rsc
CC=golang-codereviews
https://golang.org/cl/115860045
wheatman pushed a commit to wheatman/go-akaros that referenced this issue Jul 9, 2018
@davecheney @wheatman
runtime: add throwgo
1a73594 
Fixes golang#8380.

Also update hashmap.go to use throwgo rather than panic.

LGTM=khr
R=khr, rsc
CC=golang-codereviews
https://golang.org/cl/115860045
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
FrozenDueToAge
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@davecheney @randall77 @gopherbot