You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
std::span, std::byte, char8_t and such are currently supported in a lot of compilers out there and I feel like mio would directly benefit from some of these features. Right now mio implements a source/sink pattern for its common use case and uses char/unsigned char specializations and implements the begin, cbegin, rbegin, crbegin interface where instead it could be implementing a more robust API using std::byte, char8_t types and std::span. These features are spread across C++14,17,20 though and would break the underlying C++11 nature of the library.
Would it be possible to have conditional language spec detection to add support for some of these features? Or should the library be "broken" to a newer version of C++?
The text was updated successfully, but these errors were encountered:
std::span
,std::byte
,char8_t
and such are currently supported in a lot of compilers out there and I feel like mio would directly benefit from some of these features. Right now mio implements a source/sink pattern for its common use case and useschar
/unsigned char
specializations and implements thebegin
,cbegin
,rbegin
,crbegin
interface where instead it could be implementing a more robust API usingstd::byte
,char8_t
types andstd::span
. These features are spread across C++14,17,20 though and would break the underlying C++11 nature of the library.Would it be possible to have conditional language spec detection to add support for some of these features? Or should the library be "broken" to a newer version of C++?
The text was updated successfully, but these errors were encountered: