Sorry for the yelling, but it's driving me crazy. Some time ago, PHPStorm stopped requiring @return void in the function signature PHPDoc. So, we stopped doing it. Now, it's required again??
That's the "beauty" of EAP :). Since it is an EAP it is "allowed" to happen (and from time to time will happen ]:)). It's anoying, but that is your own (as well as mine own) decision to use EAP build (to take the risk that something will be broken .. again).
And this is not the first time that IntelliJ has appeared to "waffle" on a standard, and so I don't know if it's a bug or if it's their decision to remove and for how long it will be removed. I don't read every issue that is created (wow, that would be an undertaking), so I have no idea...except it disppears and reappears. Like this issue:
That's the "beauty" of EAP :). Since it is an EAP it is "allowed" to happen (and from time to time will happen ]:)). It's anoying, but that is your own (as well as mine own) decision to use EAP build (to take the risk that something will be broken .. again).
http://youtrack.jetbrains.com/issue/WI-10271
I understand about the EAP, Andriy, but I am positive that this the removal of the @return void requirement was compiled into a non-EAP version.
You are absolutely correct -- current behavior (in EAP build) is a bug.
And this is not the first time that IntelliJ has appeared to "waffle" on a standard, and so I don't know if it's a bug or if it's their decision to remove and for how long it will be removed. I don't read every issue that is created (wow, that would be an undertaking), so I have no idea...except it disppears and reappears. Like this issue:
http://youtrack.jetbrains.com/issue/WI-10486
Is it a bug? Are they changing their mind about it?
Honestly -- no idea.
On related note: http://youtrack.jetbrains.com/issue/WI-10485
Sorry, we'll make our mind and fix all contradictions.
Thanks