Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

c/driver: evaluate C++ backports library #1101

Closed
Tracked by #924
lidavidm opened this issue Sep 23, 2023 · 3 comments
Closed
Tracked by #924

c/driver: evaluate C++ backports library #1101

lidavidm opened this issue Sep 23, 2023 · 3 comments
Assignees

Comments

@lidavidm
Copy link
Member

We're stuck on C++11 due to certain R distributions; we could at least get some standard library features through backports, though, e.g. https://github.com/bitwizeshift/BackportCpp

@lidavidm lidavidm added this to the ADBC Libraries 0.8.0 milestone Sep 23, 2023
@lidavidm lidavidm self-assigned this Sep 23, 2023
@lidavidm
Copy link
Member Author

lidavidm commented Sep 23, 2023

What might be useful are

  • make_unique
  • string_view (to deal with Arrow strings)
  • span (to deal with Arrow bytestrings)
  • expected (to deal with return values in internal implementations)
  • fmt (since we do a lot of string building)

@WillAyd
Copy link
Contributor

WillAyd commented Jun 26, 2024

Worth closing now that we are on C++17?

@lidavidm
Copy link
Member Author

fmt, expected may still be useful but I think #1663 means we won't want to use expected and fmt is already there. span may be useful but isn't a big deal. So ok, let's close this.

@lidavidm lidavidm closed this as not planned Won't fix, can't repro, duplicate, stale Jun 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants