-
-
Notifications
You must be signed in to change notification settings - Fork 81
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support nullable types #19
Comments
Surely resolving the fact that Originally posted by @djmattyg007 at zendframework/zend-code#85 (comment) |
@djmattyg007 I reported the issue completely independently from other issues. Originally posted by @Ocramius at zendframework/zend-code#85 (comment) |
My point was that PHP 7.0 compatibility should be targeted before PHP 7.1 compatibility. Originally posted by @djmattyg007 at zendframework/zend-code#85 (comment) |
Ah yes, that is because the codegen part of this component is already 7.0 compatible. I hardly ever use the scanner, as it is not AST-based (which makes it very unstable) Originally posted by @Ocramius at zendframework/zend-code#85 (comment) |
If no one is maintaining the scanning code, shouldn't it be removed? Originally posted by @djmattyg007 at zendframework/zend-code#85 (comment) |
No longer needed as per #58 |
As per PHP 7.1, it is possible to define nullability of a type by adding a
?
in front of it ( https://wiki.php.net/rfc/nullable_types ).A few heads-up:
?Foo $bar = null
vs?Foo $bar
vsFoo $bar = null
TypeGenerator
to include the?
in it (not sure yet)Originally posted by @Ocramius at zendframework/zend-code#85
The text was updated successfully, but these errors were encountered: