Re: o3tl::make_unsigned

On Friday 31 of January 2020, Stephan Bergmann wrote:
> If you want to follow down the "Unsigned considered harmful" path,
> another option that may long-term prove more fruitful then that
> o3tl::make_signed could be an o3tl::ssize mimicing C++20 std::ssize
> (<http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2019/p1227r2.html>
> "P1227: Signed ssize() functions, unsigned size() functions (Revision
> 2)"; and being replaced by the true std::ssize once generally
> available), and updating relevant places in the code to use that.
> (Where occurrences of o3tl::make_unsigned would likely be good starting
> points to hunt for such places.  As discussed elsewhere in this thread,
> that should get rid of many, if not most of the current uses of
> o3tl::make_unsigned.)

 I'm fine with this if this would be ok for you (the way I see it, this 
o3tl::ssize() would be basically my proposed o3tl::make_signed() with a 
different name).

-- 
 Luboš Luňák
 l.lunak@collabora.com