Eric Niebler

So, leave `Boolean` as it currently is and get experience? My only problem with that is that going from `Boolean` to `Integral` is a tightening. And making type-checking stricter is...

> I'd almost prefer to require exactly bool and relax it only if people scream. I'm *way* too 🐔 for that. I want Ranges TS to ship in Toronto. I...

> more subtle things like "`Integral`s have only constant-time operations" and "`Integral`s are cheaper to pass by value than by reference," and "`Integral`s can be non-type template parameters." (In fairness,...

I'd like to suggest another tact here. Probably my biggest problem with `Boolean` right now is the likely effect it has on compile times. If we permitted an implementation that...

LEWG voted in Cologne to replace `Boolean` with `convertible_to`. TODO: bring a paper to Belfast.

In a manner of speaking, yes, I suppose so. But the other range adaptors support pipe syntax. And `view::counted` just _feels_ more like a factory than an adaptor. Feel free...

Proposed resolution =============== From the `filter_view` synopsis in [range.filter.view], remove the following constructor; ```diff -template -  requires viewable_range && constructible_from -constexpr filter_view(R&& r, Pred pred); ``` And strike  [range.filter.view]/p2. From...

I've never played with the API, but this is kinda fun. https://api.github.com/repos/ericniebler/stl2/issues?labels=P1,new Returns JSON for all our new P1 issues. :-)

I think we made a few converts in LWG to putting the issues lists on github and using tags. A tool to import the issues would also be a boon....

Also, review the places where `std::iterator_traits` is specialized (`common_iterator`, `counted_iterator`), and the places where `std::iterator_traits::iterator_category` is used, and look for problems.