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.

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

Document how try works, and what resume is doing #1274

Closed
briandfoy opened this issue Apr 9, 2017 · 2 comments
Closed

Document how try works, and what resume is doing #1274

briandfoy opened this issue Apr 9, 2017 · 2 comments
Labels
docs Documentation issue (primary issue type) update part of "docs" - indicates this is an update for an existing section; rewrite, clarification, etc.

Comments

@briandfoy
Copy link
Contributor

I can't give a better title for this issue because there are so many hidden things I'm still unaware of. Jonathan explained some of them in his answer to Should this Perl 6 CATCH block be able to change variables in the lexical scope?.

@briandfoy briandfoy added the docs Documentation issue (primary issue type) label Apr 9, 2017
@coke coke added the update part of "docs" - indicates this is an update for an existing section; rewrite, clarification, etc. label Aug 26, 2017
@AlexDaniel
Copy link
Member

AlexDaniel commented Sep 3, 2017

Can we have a todo list of things that should be done? I'll start:

  • use fatal is not mentioned

@tbrowder
Copy link
Member

tbrowder commented Mar 25, 2018

This resume section example mentioned by @AlexDaniel needs to be shown in a loop or other block to clearly show control flow with output.

@JJ JJ removed the JJ TPF Grant label May 14, 2018
JJ added a commit that referenced this issue Jul 1, 2018
JJ added a commit that referenced this issue Jul 1, 2018
@JJ JJ closed this as completed in 5729fa3 Jul 1, 2018
JJ added a commit to JJ/my-raku-examples that referenced this issue Jul 1, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs Documentation issue (primary issue type) update part of "docs" - indicates this is an update for an existing section; rewrite, clarification, etc.
Projects
None yet
Development

No branches or pull requests

5 participants