[ 
https://issues.apache.org/jira/browse/ARROW-8480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17156899#comment-17156899
 ] 

Mahmut Bulut commented on ARROW-8480:
-------------------------------------

Suggested API can't be used until it stabilizes. So leaving this open until it 
stabilizes. Tracking issue: [https://github.com/rust-lang/rust/issues/32838]

> [Rust] There is no check for allocation failure
> -----------------------------------------------
>
>                 Key: ARROW-8480
>                 URL: https://issues.apache.org/jira/browse/ARROW-8480
>             Project: Apache Arrow
>          Issue Type: Bug
>          Components: Rust
>            Reporter: Paddy Horan
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Reported by bluss on Github:
> [https://github.com/rust-ndarray/ndarray/issues/771]
>  
> "What I can see, there is no check for allocation success, so any buffer can 
> be created with a null pointer, which leads to soundness problems in most 
> methods. Best look into using {{std::alloc::handle_alloc_error}} or 
> alternatives. (This problem means that the mutablebuffer is not a safe 
> abstraction, and it should preferably not be exposed as public API like 
> this.)"



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to