You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@arrow.apache.org by "Chao Sun (JIRA)" <ji...@apache.org> on 2019/02/26 01:07:00 UTC

[jira] [Commented] (ARROW-4678) [Rust] Minimize unstable feature usage

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

Chao Sun commented on ARROW-4678:
---------------------------------

I don't think we can remove specialization right now. It's been used in many places. 

> [Rust] Minimize unstable feature usage
> --------------------------------------
>
>                 Key: ARROW-4678
>                 URL: https://issues.apache.org/jira/browse/ARROW-4678
>             Project: Apache Arrow
>          Issue Type: Improvement
>          Components: Rust
>    Affects Versions: 0.12.0
>            Reporter: Steven Fackler
>            Priority: Major
>
> The Rust implementation currently uses quite a few nightly features. This is unfortunately a hard blocker on using these crates for many users.
> Here's the list of currently use nightly features:
>  * type_ascription: Unused, can be trivially removed.
>  * rustc_private: Unused, can be trivially removed.
>  * box_syntax: Indefinitely far from stabilization, trivially replaceable with Box::new.
>  * box_patterns: Indefinitely far from stabilization, replaceable with some minor restructuring of a couple of matches.
>  * serde's alloc feature: Unused, can be trivially removed.
>  * try_from: Scheduled for stabilization in Rust 1.35.
>  * specialization: Actively being worked on - maybe ~1 year timeframe?
>  * packed_simd: Actively being worked on - maybe ~1 year timeframe?
> The first set of features are easy enough to get rid of - I'll make a PR to do that (https://github.com/sfackler/arrow/tree/more-stable). I'm a bit less sure of what to do with specialization and packed_simd, though.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)