It's not the best example, but Ruby is the only language I can think of where an expression (e) fails to parse but ((e)) parses.

I find that it encourages a bad kind of code golf that leads to hard to maintain code.