Christopher Di Bella
Christopher Di Bella
**Describe the bug** Per the adoption of [P1870], `ranges::begin` and `ranges::end` depend on `enable_safe_range`, but this library doesn't have `enable_safe_range`. **Acceptance criteria** `ranges::begin` and `ranges::end` should both depend on `enable_safe_range`,...
```cpp template constexpr auto operator()(T&& t) const CJDB_DEDUCE_NOEXCEPT({ return process(t); }) ``` is much easier to grok and makes the function feel more natural than what is currently in place....
**Is your feature request related to a problem? Please describe.** Not everyone uses Conan. It'd be nice if there was an alternative package manager that's more lightweight, and this will...
**Is your feature request related to a problem? Please describe.** The current mechanism for checking `C2` subsumes `C1` is completely ad-hoc. It'd be great for there to be a more...
Once `std::format` and constexpr `std::string` are supported by the implementation, move to those, and possibly even `fmt::print`.
libc++ doesn't support `source_location` yet. Once it does, move away from `__FILE__` and `__LINE__`.
clang-tidy doesn't seem to respect feature-test macros, but part of the design is done so that clang-tidy doesn't see through attempts to force a compile-time error (e.g. not using `static_assert`...
The top-level namespace `ranges` will have the potential to clash with `std::ranges`, if people want to shorten `std::ranges` to `ranges`. To prevent creativity and fragmented namespace aliases, I propose that...
`istream_view` is only useful if the input to be formatted on read and `std::istreambuf_iterator` only works with types that have a `std::char_traits` specialisation. The purpose of `unformatted_istream_view` is to read...