Fixing incorrect rendering of pipe character

[SoniaLopezBravo]

This closes #352

[SoniaLopezBravo]

@bettinaheim @tcNickolas @cgranade Could you review this? Thanks!

[tcNickolas]

This approach doesn't seem to work when viewing the files on GitHub: looking at https://github.com/microsoft/qsharp-language/blob/740b3427d7be2f8bcba1e9c14675d82b16590143/Specifications/Language/3_Expressions/PrecedenceAndAssociativity.md, it renders as

If we want it to be viewable both in the docs and in the GitHub version of the files, we might have to do some kind of processing in the documentation generation pipeline to account for this difference.

[SoniaLopezBravo]

@tcNickolas I have changed it for another of the possible solutions. This one renders ok on GitHub files, hope it does on the docs page too.

[tcNickolas]

Can you open a pull request with a matching change on the docs repo so that we get a preview to check whether this solution works indeed?

[SoniaLopezBravo]

Can you open a pull request with a matching change on the docs repo so that we get a preview to check whether this solution works indeed?

Hi @tcNickolas. I have created this matching PR, in the preview we see that the pipe character is rendering ok :)

[tcNickolas]

Great, looks like this solution works both on GitHub and in the docs!
Just one small comment: let's keep the whitespace between ? and |, since they are not a single operator like |||, but rather two parts of an operator that have an expression between them.

[SoniaLopezBravo]

@bettinaheim could you review this?

[alan-geller]

Looks good to me.

[bettinaheim]

I believe this is addressed by the now merged PR #124. I'll hence close this.