1+++ 2title = "Acknowledgements" 3description = "Giving thanks to those who made Outcome happen" 4+++ 5 6## github contributors 7 8{{%ghcontributors "https://api.github.com/repos/ned14/outcome/contributors?per_page=100" %}} 9 10## This pretty, modern C++ documentation 11 12* [Hugo](https://gohugo.io) - static website generator of this documentation. 13* [hugo-theme-docdock](https://github.com/vjeantet/hugo-theme-docdock) - the Hugo theme used by this documentation. 14* [Standardese](https://github.com/foonathan/standardese) - the API reference generator (up until Outcome v2.0) 15 16# Special thanks for Outcome v2.1 17 18Once again Andrzej Krzemienski stands out for a never ceasing flow of excellent questions, 19"what if?"'s, eagle eyed spotting of corner case logic bugs, and design contradictions. 20Thank you Andrzej! 21 22My thanks to the Microsoft Visual C++ compiler team for incorporating Outcome into the 23MSVC test suite, and thus finding many interesting corner case quirks in how best to 24interpret the C++ standard. In some cases, Outcome was refactored to be less ambiguous; 25in others, defects had to be submitted to WG21 because the standard wording was not clear. 26The Visual C++ compiler team were particularly generous with their time in helping track 27down the cause of these issues, complete with submitting pull requests with bug fixes. 28I am very grateful to them. 29 30# Special thanks for Outcome v2.0 31 32For a second time, Charley Bay stepped up as review manager. Given how much work it was 33for the v1 review, I can only say **thank you**. 34 35Andrzej Krzemienski went far beyond the call of duty in the development of Outcome v2. 36He wrote the front page, and the start of the tutorial. He thus set the tone, pacing, 37style and form of the tutorial which I merely continued for the rest of the tutorial. 38He also volunteered considerable amounts of his time as as primary peer reviewer for 39the v2 design and implementation, asking many very valuable "stupid questions" at least 40one of which caused a major rethink and refactor. If Outcome v2 passes its second peer 41review, it's because of Andrzej. Thank you. 42 43Jonathan Müller invested countless hours in his doxygen replacement tool Standardese 44which Outcome uses to generate the reference API docs, and a not insignificant number 45of those went on fixing issues for Outcome. Thank you. 46 47# Special thanks for Outcome v1 48 49To Paul Bristow who <a href="https://lists.boost.org/Archives/boost/2015/05/222687.php"> 50proposed the name "Outcome"</a> for the library after a very extended 51period of name bikeshedding on boost-dev. I had been minded to call the library "Boost.Donkey" 52just to shut everyone up because the name bike shedding was getting ridiculous. But 53Outcome is a lot nicer, so thank you Paul. 54 55My heartfelt thanks to Charley Bay for acting as review manager for Outcome in May 2017. 56It is becoming ever harder to find a Boost review manager, so thank you! My thanks also 57to the CppCast team Rob Irving and Jason Turner for so quickly getting me on to CppCast 58to discuss `expected<T, E>` during the Outcome peer review to help publicise the review. 59 60More general thanks are due to those on boost-dev, Reddit and SG14 for extensive and often very detailed 61feedback on the library pretty much from its beginning. You are all too numerous to 62remember, but certainly Tongari and Andrzej Krzemienski come to mind as having engaged 63in particularly long discussion threads with tons of useful feedback which clarified my 64thinking. Andrzej also went through the documentation with a fine toothed comb before the 65review, finding many small errata and confusing wording. 66 67Finally, my thanks to Vicente for driving Expected from its beginnings to hopefully 68standardisation before 2020. It's many years of work getting something standardised, even 69more years than getting a library into Boost which as you can see from the history above 70took about three years. 71