You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now that the PR #102 is merged, I have another question concerning casts. I noticed that (unset) $foo is parsed as an unset node instead of a cast node with type unset. While this is workable for the prettier integration, i still found it a bit confusing - especially because the difference bettween the unset cast and a regular call like unset($foo) is just that the first one has a single node in arguments, while the second one has a list.
Thanks in advance 😄
The text was updated successfully, but these errors were encountered:
Noooo, it's not good to prettier, it's a real BUG, I may did not pay enough attention on it !!!
Example #2 Using (unset) casting
(unset) casting is often confused with the unset() function. (unset) casting serves
only as a NULL-type cast, for completeness. It does not alter the variable it's casting.
Now that the PR #102 is merged, I have another question concerning casts. I noticed that
(unset) $foo
is parsed as anunset
node instead of a cast node with typeunset
. While this is workable for the prettier integration, i still found it a bit confusing - especially because the difference bettween the unset cast and a regular call likeunset($foo)
is just that the first one has a single node inarguments
, while the second one has a list.Thanks in advance 😄
The text was updated successfully, but these errors were encountered: