streams: Re-add support for arbitrary metadata for stream notifier functions #19158
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Support for attaching arbitrary metadata for consumption by stream notifier functions got broken in #19024 when the previous
zval ptr
got changed tozend_fcall_info_cache *fcc
, making the data specific to theuser_space_stream_notifier
.Fix this by changing the field to
void *ptr
, avoiding the indirection through azval
, but preserving the ability to store arbitrary data. If necessary to support different types thanIS_PTR
, extensions can heap-allocate azval
to store within->ptr
as a minimal change to keep compatibility with PHP 8.4 or lower.