Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I'd say this is a fairly common sense thing to do. Whitespace styles have no effect on identifier names or anything else that could alter compatibility between different pieces of Zig code. It's also something that's incredibly easy to alter after the code is written: just put the code through a formatter and you're done. Besides, there are reasonable reasons for using both spaces and tabs for indenting: it's not as if one is objectively better than another. Compiler errors should be reserved for things that are objectively incorrect or have the ability to produce compatibility problems (such as non-standard case in public identifier names), not superficial styling choices.