Representation for durations and time_points

About direct parsing, the documentation states that:

> The drawback of this approach is that fully custom type representations are not supported, only the library-provided conversions are.

I wonder where this limitation stands?

I have a described struct with an `std::chrono::duration` member. While I have the proper tag_invoke overloads, since there is no built-in conversion support for std::chrono, I can't use `parse_into`. Is that correct?

Would it be possible to add new customization points to allow direct parsing of custom types?

Any chance to add a conversion category for date /time / duration (if that make sense)?

Start with the direct-parsing documentation and the parse_into and tag_invoke entry points mentioned in the issue. First establish whether custom std::chrono representations and a date/time/duration conversion category are supported; the work is done only after a concrete API direction and acceptance criteria are agreed.

Written by the indexing model from the issue text.