id,summary,reporter,owner,description,type,status,milestone,component,version,severity,resolution,keywords,cc
10992,Chrono IO state savers inconsistent with Boost.IO state savers,rkawulak,viboes,"The constructors of Boost.IO state savers taking the second new_value argument set the state to the new_value immediately and restore the previous state upon destruction. OTOH, the Boost.Chrono IO state savers do something different (and arguably unintuitive): they don't alter the state upon construction at all and restore the state to new_value rather than the previous state upon destruction. The behaviour should be aligned with that of Boost.IO to avoid confusion and make it more useful.",Bugs,closed,Boost 1.58.0,chrono,Boost Development Trunk,Problem,fixed,,