True, I guess I was expecting if you were reimplementing these with additional protections, why not add the protection using the custom pointer reimplementations to ensure no use after frees. Seems like a missed opportunity.
Does the StringView/Span implementation here seem lacking? If the underlying data goes away, wouldn't the pointer now point to an invalid freed location, because it doesn't track the underlying data in any way?
Maybe it's just me, but I'd rather teach how to use a knife safely? And a cut from a blade is a lesson to be learned, hopefully only once.
Edit: Oh and if anyone's looking for the tool name, it's called a nibbler. This one is just table-mounted, there are power tool and unpowered versions ofc.