[ https://issues.apache.org/jira/browse/ARROW-4678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17661700#comment-17661700 ]
Rok Mihevc commented on ARROW-4678: ----------------------------------- This issue has been migrated to [issue #21208|https://github.com/apache/arrow/issues/21208] on GitHub. Please see the [migration documentation|https://github.com/apache/arrow/issues/14542] for further details. > [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 > Assignee: Steven Fackler > Priority: Major > Labels: pull-request-available > Fix For: 0.13.0 > > Time Spent: 20m > Remaining Estimate: 0h > > 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 (v8.20.10#820010)