When your question is answered use !solved to mark the question as resolved.
Remember to ask specific questions, provide necessary details, and reduce your question to its simplest form. For tips on how to ask a good question use !howto ask.
#My custom int parser can't handle std::numeric_limits<T>::min()
untold stormBOT
novel steppe
for embedded environments, you can use std::istringstream maybe?
These can overflow, and work only when dealing with positive values, fix them
barren cave
for embedded environments, you can use std::istringstream maybe?
id rather not use stringstream, i want to use string_view instead
novel steppe
id rather not use stringstream, i want to use string_view instead
homie, pass the string_view into the istringstream
ez
barren cave
its more expensive, no?
also stringstream doesnt do validation?
i need a boolean back
novel steppe
also stringstream doesnt do validation?
it does perfect validation, check the error flags
novel steppe
AH, yeah no id rather not deal with global error flags
no mate, local error flags inside the istringstream
barren cave
Unfortunately, iostreams is not for performance-intensive work. The problem is not copying things in memory (copying strings is fast), it's virtual function dispatches, potentially to the tune of several indirect function calls per character.
id rather not
its more expensive
novel steppe
its more expensive
oh wait, so you want to parse these numbers with some good performance? manually digiy by digit?
novel steppe
if yes, then fix your loops and integer overflow issues
barren cave
I fixed it #1332165041637822485