id	summary	reporter	owner	description	type	status	milestone	component	version	severity	resolution	keywords	cc
8691	iostate is not checked after scan_keyword call	tmmikolajczyk@…	viboes	"Implementation of the duration_get::do_get_n_d_valid_unit and duration_get::do_get_valid_unit methods calls chrono_detail::scan_keyword and then unconditionally calls the facet.match_n_d_valid_unit and facet.match_valid_unit methods appropriately, no matter what is the value of the iostate flag.
IMO, the function should just return value ""i"" if iostate is not good after the scan_keyword call.
The proposed change is attached as a patch. The patch fixes also typos in doxygen comments of those functions."	Bugs	closed	Boost 1.54.0	chrono	Boost Development Trunk	Problem	fixed