[I] Fallible MemoryPool claim and reserve methods? [arrow-rs]

["jhorstmann (via GitHub)" <gi...@apache.org>]

jhorstmann opened a new issue, #10753:
URL: https://github.com/apache/arrow-rs/issues/10753

   ### Is your feature request related to a problem or challenge?
   
   Under strict memory limits, it seems there would currently be a time-of-check vs time-of-use issue between checking `available` memory vs `reserve`ing it. Fallible `reserve` and `claim` methods could avoid that.
   
   ### Describe the solution you'd like
   
   _No response_
   
   ### Describe alternatives you've considered
   
   _No response_
   
   ### Additional context
   
   _No response_


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: github-unsubscribe@arrow.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [I] Fallible MemoryPool claim and reserve methods? [arrow-rs]

["Rich-T-kid (via GitHub)" <gi...@apache.org>]

Rich-T-kid commented on issue #10753:
URL: https://github.com/apache/arrow-rs/issues/10753#issuecomment-5488733022

   🤔 would be nice to have especially when allocators become more usable in rust


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: github-unsubscribe@arrow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org