> I'll write QOptional tomorrow or on Wednesday, after I've had the chance > to read the proposal to C++14 (that was dropped).
What would the plan for handling value access on unset options be? std::optional<> throws an exception. I initially did the same when implementing an Optional<T> class but ran into the kind of issue described here: http://stackoverflow.com/questions/13777446/ios-how-to-get-stack-trace-of-an-unhandled-stdexception qFatal() seems like the simple and obvious approach. Regards, Rob. On 4 February 2014 03:40, Thiago Macieira <[email protected]> wrote: > Em seg 03 fev 2014, às 16:26:21, Thiago Macieira escreveu: >> Sure. Adding Qt's dev list. I've begun the work, starting with making a >> template version of those functions. See: >> >> https://codereview.qt-project.org/77277 > > Make that: > > https://codereview.qt-project.org/77278 > https://codereview.qt-project.org/77279 > https://codereview.qt-project.org/77280 > https://codereview.qt-project.org/77281 > https://codereview.qt-project.org/77282 > https://codereview.qt-project.org/77277 > https://codereview.qt-project.org/77283 > > 280 and 281 are dust-offs of code I've had for some time but had never > submitted for review. It's good to get them out in the open. > > I'll write QOptional tomorrow or on Wednesday, after I've had the chance to > read the proposal to C++14 (that was dropped). But I fear I won't have the > time to solve the issue of mixing it with QVariant properly before the feature > freeze. > -- > Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org > Software Architect - Intel Open Source Technology Center > PGP/GPG: 0x6EF45358; fingerprint: > E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358 > > _______________________________________________ > Development mailing list > [email protected] > http://lists.qt-project.org/mailman/listinfo/development > _______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
