[SG16-Unicode] It’s Time to Stop Adding New Features for Non-Unicode Execution Encodings in C++
Ville Voutilainen
ville.voutilainen at gmail.com
Sat Apr 27 15:09:12 CEST 2019
On Sat, 27 Apr 2019 at 15:44, Lyberta <lyberta at lyberta.net> wrote:
> > Both std::optional and std::span provide 'safe' ways for extracting
> > and indexing.
> Last time I checked, std::span doesn't have at().
That's correct. To do 'safe' indexing, you need to do a range-check
before the indexing.
That doesn't mean it's not 'safe'.
More information about the Unicode
mailing list