Re: Should boost::core::string_view be made public?

From: g.peterhoff_at_[hidden]
Date: 2024-02-14 22:23:08

Have you come to a conclusion how this should be handled (in the future)?

The problem is basically that there are different implementations for string_view.
I don't know why it was done this way. Presumably it's because various boost libraries want to be independent of others, so that some things are implemented anew each time (within the library) instead of using existing libraries. This will also be due to the fact that boost is not atomistic enough, so that large libraries might have to be included/used, although only a fraction of the functionality is needed.

My suggestion:
- Throw out boost::utility::string_view
- Make boost::core::detail::string_view public, just like all other backports in boost::core.
- Check if there are other multiple implementations. If so, pull them out into separate small boost libraries. (For databases, this would be called normalization, but it must not be over-normalized).

regards
Gero