I miss descriptions about interfaces and (base) classes and their relationships for a key feature like parsing/data analysis.
Would you like to extend your published explanations?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I apologise for not responding sooner. For a bunch of reasons I won't bore you with, I've been unable to apply much/any attention to any of my open-source projects this year. However, things have calmed down for me now, and for the next few months I have sufficient time to catch up on outstanding issues. If you're still interested in this issue, I'd be happy to talk more about it in the next few weeks.
Matt
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I repeat my feature request "Clarifications for parsing interfaces" here as requested for this discussion interface.
The class "fastformat::format_parsing_exception" is scantily described.
Your article "C++ and format_iterator" (from 2010-06-02) explains some details.
I miss descriptions about interfaces and (base) classes and their relationships for a key feature like parsing/data analysis.
Would you like to extend your published explanations?
Markus
I apologise for not responding sooner. For a bunch of reasons I won't bore you with, I've been unable to apply much/any attention to any of my open-source projects this year. However, things have calmed down for me now, and for the next few months I have sufficient time to catch up on outstanding issues. If you're still interested in this issue, I'd be happy to talk more about it in the next few weeks.
Matt
Thanks for your feedback. - A single message would have been sufficient about the situation (in a private mail).
Now I am curious if a discussion can be continued in constructive ways.