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
Currently, SwapEndianArrayData() will always allocate new buffers from the default memory pool. It should instead conform to other allocating functions and accept a MemoryPool* argument:
### Rationale for this change
Add memory_pool argument in `SwapEndianArrayData` to avoid allocating all from default memory pool.
### What changes are included in this PR?
Add memory_pool argument in `SwapEndianArrayData`
### Are these changes tested?
Maybe tested by ipc
### Are there any user-facing changes?
Maybe user would use the new interface
* Closes: #35511
Authored-by: mwish <maplewish117@gmail.com>
Signed-off-by: Antoine Pitrou <antoine@python.org>
…pache#36431)
### Rationale for this change
Add memory_pool argument in `SwapEndianArrayData` to avoid allocating all from default memory pool.
### What changes are included in this PR?
Add memory_pool argument in `SwapEndianArrayData`
### Are these changes tested?
Maybe tested by ipc
### Are there any user-facing changes?
Maybe user would use the new interface
* Closes: apache#35511
Authored-by: mwish <maplewish117@gmail.com>
Signed-off-by: Antoine Pitrou <antoine@python.org>
Describe the enhancement requested
Currently,
SwapEndianArrayData()
will always allocate new buffers from the default memory pool. It should instead conform to other allocating functions and accept aMemoryPool*
argument:Component(s)
C++
The text was updated successfully, but these errors were encountered: