I made 2 PRs because some pages are not in x/website but in this repo instead. To prevent this in future, maybe I can create a test checking contents inside every <pre> tag for tabs. I could suggest to create a replacer instead, but there are some cases when it will result in messed indentation, e.g. in the spec. What do you think?
What did you expect to see?
What did you see instead?
The text was updated successfully, but these errors were encountered:
@ianlancetaylor most of the code on the website is written with tabs which are equal to 4 real spaces, that’s why I assumed it as the correct choice. The reason behind this likely that all major modern browsers render tab 8 characters wide. In editors and IDEs one can choose whatever width she wants. Since the only purpose of tab indentation is readability, I think 4-characters width performs its role well because code snippets have both small height and nesting. But I would happily turn them into real tabs, consistency is the only concern I have