Skip to content

docs: convert Backtracing.rst to Markdown #64628

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

MaxDesiatov
Copy link
Contributor

@MaxDesiatov MaxDesiatov commented Mar 26, 2023

The rendered Markdown document looks identical to the original .rst document, except:

  • The original rendered some lists within blockquotes, which looked and parsed semantically wrong. Blockquotes on these lists were removed.
  • In the Markdown version a footnote within the configuration table is natively supported.
  • When rendered on GitHub, the "System specifics ➡ macOS" table does not render header colspan, but this is supported in DocC thanks to add support for colspan/rowspan in tables swift-cmark#46

Resolves partially #49997.

@MaxDesiatov MaxDesiatov force-pushed the maxd/backtracing-markdown branch from 50c7eb8 to fbbb560 Compare March 26, 2023 17:52
Copy link
Collaborator

@AnthonyLatsis AnthonyLatsis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry for the delay.

frames at the bottom of the stack where the actual fault occurred.

1. There are `limit` or fewer frames. In this case we will display all
the frames in the backtrace. Note that this \_[includes]() the case
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think "includes" was meant to be in italic here.

Comment on lines +72 to +82
1. There are `limit` or fewer frames. In this case we will display all
the frames in the backtrace. Note that this \_[includes]() the case
where there are exactly `limit` frames.
2. There are more than `limit` frames.
1. `top` is `0`. We will display the first `limit - 1` frames
followed by `...` to indicate that more frames exist.
2. `top` is less than `limit - 1`. We will display
`limit - 1 - top` frames from the bottom of the stack, then a
`...`, then `top` frames from the top of the stack.
3. `top` is greater or equal to `limit - 1`. We will display `...`,
followed by `limit - 1` frames from the top of the stack.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How about changing all these bullet introducers to 1. and letting the renderer take care of enumerating them instead?

should contain a `,`-separated list of `key=value` pairs. Supported keys
are as follows:

| Key | Default | Meaning |
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would it hurt the rendered result if we shrink the tables horizontally as in the old file to ease reading the raw text?

@MaxDesiatov
Copy link
Contributor Author

Sorry for the delay.

No problem at all, I still would like to get document author's approval first 🙂

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants