-
Notifications
You must be signed in to change notification settings - Fork 7.8k
Type error could print false
/true
type/value instead of bool
#8329
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
Comments
false
type must be printed instead of bool
false
/true
type must be printed instead of bool
false
/true
type must be printed instead of bool
false
/true
type/value must be printed instead of bool
false
/true
type/value must be printed instead of bool
false
/true
type/value instead of bool
I think that's pretty resonable. At least for the binary boolean which has not much information which can "leak" in error messages (unlick if you were to dump the string contents for example). |
yes, this issue is solely for |
kocsismate
added a commit
to kocsismate/php-src
that referenced
this issue
Apr 16, 2022
kocsismate
added a commit
to kocsismate/php-src
that referenced
this issue
Apr 16, 2022
kocsismate
added a commit
to kocsismate/php-src
that referenced
this issue
Apr 16, 2022
kocsismate
added a commit
to kocsismate/php-src
that referenced
this issue
Apr 16, 2022
kocsismate
added a commit
to kocsismate/php-src
that referenced
this issue
Jan 21, 2023
kocsismate
added a commit
to kocsismate/php-src
that referenced
this issue
Jan 21, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
https://3v4l.org/av8Mi
since https://wiki.php.net/rfc/null-false-standalone-types PHP already standalone supports
false
typestarting with (if accepted) #8326
true
as a standalone type will be supported as wellThis is a feature request to improve the error messages with more specific type to help the developer understand the real given value.
So instead of:
the following should be printed:
The text was updated successfully, but these errors were encountered: