Fix #124 Require parenthesis around clone()

[mbeccati]

Per request from @Crell on Discord ;-)

Resolves #124

[Crell]

I'm good with this. Waiting a few days for other WG members to comment if desired.

[mbeccati]

@jrfnl I'm not a native speaker, but to me it feels used would be more appropriate than called when referring to a language construct (vs function). Thoughts?

[jrfnl]

@jrfnl I'm not a native speaker, but to me it feels used would be more appropriate than called when referring to a language construct (vs function). Thoughts?

@mbeccati I agree, used reads better.

[jrfnl]

Question for the interpretation by tooling:

The examples have no spacing between the keyword and the open parenthesis and on the inside of the parentheses.

Can we conclude that the rule about this for function/method calls (line 781 - 785) also applies to these language constructs ?

When making a method or function call, there MUST NOT be a space between the
method or function name and the opening parenthesis, there MUST NOT be a space
after the opening parenthesis, and there MUST NOT be a space before the
closing parenthesis. In the argument list, there MUST NOT be a space before
each comma, and there MUST be one space after each comma.

[mbeccati]

@jrfnl How about something along the lines of

Suggested change

	not provided. For example:
	not provided. As such, it follows the same rules as function calls. For example:

[jrfnl]

I'm not sure it needs to be spelled out as this paragraph is within the "function and method call" section anyway, but I just wanted to clarify to avoid ending up with discussions about this in the PHPCS repo later on.

[Crell]

Agreed with @jrfnl about the spacing. Pseudo-function language constructs should always be formatted like functions, without a space.