This October's mailing has lots and lots of WG21 papers related to Outcome which were strongly influenced by the peer review here in May. Boost members who contributed to the Outcome v1 review in May should please take a bow and accept thanks for spurring so much discussion and debate regarding these potential future C++ features. Thank you. 1. http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2017/p0323r3.pdf Utility class to represent expected object 2. http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2017/p0650r1.pdf C++ Monadic interface 3. http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2017/p0762r0.pdf Concerns about expected from the Boost.Outcome peer review 4. http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2017/p0779r0.pdf Proposing operator try() (with added native C++ macro functions!) 5. http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2017/p0786r0.pdf SuccessOrFailure, ValuedOrError and ValuedOrNone types 6. http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2017/p0824r0.pdf Summary of SG14 discussion on : towards exception-less error handling Niall -- ned Productions Limited Consulting http://www.nedproductions.biz/ http://ie.linkedin.com/in/nialldouglas/