Trigger syntax highlighting for code examples

[patrickmckenna]

Suggestion: make use of syntax-highlighting available in GitHub-flavored Markdown.

Example current view:

Example with syntax highlighting:

Note: many of the current code examples use indentation, rather than fenced code block syntax, to trigger monospace rendering. Those examples would need to be converted to fenced code blocks to get syntax highlighting.

Happy to open a PR if this is desired.

[gdr-at-ms]

Thanks for the suggestion.
It is noteworthy that this is an issue that divides reasonable people, especially the larger C++ community, in many ways. Some people wonder if we should similarly systematically highlight verbs and nouns in every English sentence we write :-)
For now, we are doing without syntax highlighting, but we will definitely keep syntax highlighting in mind (e.g. comments formatted differently).

The issue about fenced code block syntax is more substantive, I think. It would require lot of work to fix, but I suspect having an open issue won't hurt. Thanks!

[Kristine1975]

Just for the record: It apparently (I havent't tested it) is possible to turn off syntax highlighting in Github:

1. Install the Stylish browser-addon (Firefox, Chrome).
2. Use this stylesheet.

[torbjoernk]

FYI: there is already a massive PR for this: #96

[Liryna]

@torbjoernk ty, I haven't found this issue before making the PR :D
The PR is massive because I removed all first tabulations that become useless after moving to syntax highlighting.

@gdr-at-ms,
The PR should be review quickly or there will be easily some conflict to fix.

[gdr-at-ms]

@Liryna Yes; we have all been busy this week; will get to that.

[AndrewPardoe]

We prefer the simple, non-syntax highlighted code blocks for the time being. Thank you, @Liryna, for making the PR but we're not merging it at the time. Sorry!

[tkruse]

Since @gdr-at-ms said "The issue about fenced code block syntax is more substantive, I think. It would require lot of work to fix, ..."
I hope you realize you can take the PR by @Liryna, then run find/replace

```c++\n -> ```\n

and you're done.

[skyrpex]

what's the reason for not using syntax highlighting in the documentation?

[blakehawkins]

@skyrpex not all flavors of markdown support such a thing. In a word: portability.