[
https://issues.apache.org/jira/browse/ARROW-5404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17662428#comment-17662428
]
Rok Mihevc commented on ARROW-5404:
-----------------------------------
This issue has been migrated to [issue
#16742|https://github.com/apache/arrow/issues/16742] on GitHub. Please see the
[migration documentation|https://github.com/apache/arrow/issues/14542] for
further details.
> [C++] nonstd::string_view conflicts with std::string_view in c++17
> ------------------------------------------------------------------
>
> Key: ARROW-5404
> URL: https://issues.apache.org/jira/browse/ARROW-5404
> Project: Apache Arrow
> Issue Type: New Feature
> Components: C++
> Reporter: Ben Kietzman
> Assignee: Ben Kietzman
> Priority: Minor
> Labels: pull-request-available
> Fix For: 0.14.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> From GitHub issue https://github.com/apache/arrow/issues/4294
> Our vendored string_view header will forward to {{std::string_view}} if that
> is available. This can produce ABI conflicts and build errors when arrow or
> applications which use it are built against c++17.
> I think it's acceptable to just force usage of nonstd's implementation with
> {{#define nssv_CONFIG_SELECT_STRING_VIEW nssv_STRING_VIEW_NONSTD}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
