Migrating token_range_t off of boost::size

[thinlang]

No description provided.

[sean-parent]

Reason for change? Would moving token_range_t to std::basic_string_view<unsigned char> be a cleaner option?

[thinlang]

Reason for change? Would moving token_range_t to std::basic_string_view be a cleaner option?

I'm moving some Photoshop code off of boost::size. I encountered a few places where we were using boost::size on token ranges and thought it best to put a replacement closest to token_range_t rather than create a local function in Photoshop and then have 2 ways to get the size of a token range.

If I moved token range to std::basic_string_view<unsigned char>, I'd maybe need to migrate more boost than I'd anticipated but I can certainly try. Stand by.

[thinlang]

Turns out moving to string_view would require a MUCH bigger change as we raw manipulate and read the first and second members of the pair.