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

Tradução: AdvancedOperators.md - Shifting Behavior for Signed Integers #50

Open
GabrielaBezerra opened this issue Oct 3, 2022 · 0 comments
Open

Tradução: AdvancedOperators.md - Shifting Behavior for Signed Integers #50

GabrielaBezerra opened this issue Oct 3, 2022 · 0 comments
Assignees
@elisionara

Comments

@GabrielaBezerra
Copy link
Member

Traduza o conteúdo de AdvancedOperators.md - Shifting Behavior for Signed Integers
@elisionara elisionara self-assigned this Oct 6, 2022
mateusrodriguesxyz pushed a commit that referenced this issue Jan 24, 2023
@amartini51
Replace @comment blocks with HTML comments (#50)
fd82527 
This reduces the places where content in the comment causes DocC to
silently mis-parse the comment and content after it.

The markdown parser for DocC first parses plain markdown syntax, and
then identifies places where the `@Comment { }` syntax delimits blocks.
That means it tries to parse the content of a comment as markdown first,
and then later it gets turned into a comment. The parsing of HTML style
comments happens as part of the first stage, which makes it less
fragile.

Using the DocC syntax for comments, a lot of the issues seem to come
from `}` appearing in commented-out in code listings, or from other
places where part of the comment is being interpreted as markdown and
preventing the later DocC parsing pass from treating that content as a
comment, or in some causes causing content after it to be missing. Using
the HTML comment syntax, the `-->` arrow used in comment-out formal
grammar conflicts with the end-of-comment marker, which I worked around
by changing them to a `->` arrow. We can probably delete most or all of
the commented-out formal grammar blocks, which seem to date back to the
original drafting of the book's grammar.

Some of the comment-parsing issues appear to be related to a known issue
in Swift-Markdown: apple/swift-markdown#84
mateusrodriguesxyz pushed a commit that referenced this issue Jan 24, 2023
@amartini51
Replace straggler @comment syntax.
0f1599f 
One change in the HTML output -- there's no longer a stray } in Generics
just before the Generic Subscripts heading.

These got skipped over, but should have been part of commit
fd82527 for PR #50.
mateusrodriguesxyz pushed a commit that referenced this issue Jan 24, 2023
@amartini51
Fix straggler comment syntax and blank lines (#62)
f055a20 
Change some places that got didn't get fixed by PR #60 and PR #50.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@elisionara elisionara

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

When branches are created from issues, their pull requests are automatically linked.

50-tradução-advancedoperatorsmd-shifting-behavior-for-signed-integers elisionara/swift-book
2 participants
@GabrielaBezerra @elisionara