为提升可读性给正则添加额外捕获组是否存在弊端？

Great question—adding extra parentheses to clarify regex structure (especially for long, complex patterns) is a super common practice, and in most cases, it’s totally safe. Let’s break down your two examples to cover the potential tradeoffs:

1. Using Capture Groups Instead of Non-Capture Groups for Clarity #

Take your first example: you prefer \w+\.(?!(bat|exe))\w+ over the "standard" non-capture group version \w+\.(?!(?:bat|exe))\w+ because it’s easier to read.

• The good news: This is perfectly acceptable if you’re not worried about unused capture groups. The only practical difference here is that the capture group (bat|exe) will store the matched substring (either "bat" or "exe") in memory, whereas the non-capture group (?:bat|exe) doesn’t. For most everyday use cases (like validating user input, parsing small files, etc.), this tiny memory overhead is completely negligible.
• Your workflow helps: Since you use named capture groups for intentional capturing, you don’t have to worry about accidental index conflicts (like mixing up $1 from this extra group with a real capture group elsewhere). That eliminates the biggest downside of unnecessary capture groups.

2. Parentheses to Clarify Branch Boundaries #

Your second example: rewriting \w+\.psd|psd_exe as (\w+\.psd)|psd_exe to avoid misinterpretation.

This is actually a great practice! The original regex works as intended (matches file.psd or psd_exe), but without the parentheses, it’s easy for someone (including future you) to misread the branch scope—thinking it might match file.psd_exe instead. Adding parentheses here makes the exact intended branches crystal clear, which is critical for maintainability.

• Minor caveat: Again, this adds a capture group that you might not need. If you’re concerned about that (or if other people might use this regex and accidentally reference the group), you could use a non-capture group: (?:\w+\.psd)|psd_exe. But if you find the capture group syntax more readable, there’s no harm in sticking with it—just be aware that the group will store the matched file.psd substring if you ever reference it later.

Final Verdict #

Adding extra parentheses for readability is almost always worth it. The only downsides are minimal (tiny memory usage, potential confusion for other developers if they don’t know the parentheses are just for clarity) and easily mitigated by your existing workflow (using named groups for intentional captures).

At the end of the day, regexes are notoriously hard to read and maintain—any change that makes them clearer for you (and your team, if applicable) is a win.

内容的提问来源于stack exchange，提问作者samuelbrody1249