-
Notifications
You must be signed in to change notification settings - Fork 7.7k
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
Inform type in messsage: 'Illegal offset type' #10504
Inform type in messsage: 'Illegal offset type' #10504
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I had a quick scroll through the changed C code and it looks generally good, thanks.
Just some minor comments.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Other than the typo looks good.
I'll do a follow up PR to extract the offset functions into a common zend_API one as it could also fold the string offset access error into it.
After addressing the comments please do not forget to regenerate the vm by running |
Lgtm, thanks! |
Done, I think that's it. I await you. Thanks. |
About the failure in the CI, I noticed the same behavior in #10483. Appears to be cached. |
Well, now it's over, it was the same cache. The |
The failed file is |
Thank you! |
Okay, that was a typo, it was supposed to say it had nothing to do with this PR changes. Thanks for all your help, regards. |
#10432
@Girgias @nielsdos @devnexen
I apologize for my ignorance on #10450, it was not something I used in my day to day (git rebase).
I appreciate all of your help.