Skip to content

[3.8] bpo-43199: Briefly explain why no goto (GH-24852) #24863

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.

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

Merged
merged 1 commit into from
Mar 15, 2021

Conversation

miss-islington
Copy link
Contributor

@miss-islington miss-islington commented Mar 14, 2021

Answer "Why is there no goto?" in the Design and History FAQ.
(cherry picked from commit 5e29021)

Co-authored-by: Terry Jan Reedy [email protected]

https://bugs.python.org/issue43199

Answer "Why is there no goto?" in the Design and History FAQ.
(cherry picked from commit 5e29021)

Co-authored-by: Terry Jan Reedy <[email protected]>
@miss-islington
Copy link
Contributor Author

@terryjreedy: Status check is done, and it's a success ✅ .

1 similar comment
@miss-islington
Copy link
Contributor Author

@terryjreedy: Status check is done, and it's a success ✅ .

@miss-islington
Copy link
Contributor Author

@terryjreedy: Status check is done, and it's a success ✅ .

1 similar comment
@miss-islington
Copy link
Contributor Author

@terryjreedy: Status check is done, and it's a success ✅ .

@miss-islington miss-islington merged commit 59f2741 into python:3.8 Mar 15, 2021
@miss-islington miss-islington deleted the backport-5e29021-3.8 branch March 15, 2021 04:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs Documentation in the Doc dir
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants