Are SE proposals supposed to be used as documentation?

I am sorry if it sounds as a complaint (because it is not), but what is the place for Swift parts that are missing, or very scarcely documented in TSPL? Take ~Copyable or macros for example. ~Copyable didn't appear in 6.0 version of the book (I don't know about 6.1, as it is not searchable and there is no official pdf version yet, and I didn't try to generate the pdf myself yet), and I am sure that most of the readers have very vague idea how to implement macros after reading the corresponding chapter in the book.
Same goes to the concurrency chapter - most of the code doesn't work and the descriptions are very superficial. So, where is proper place to look for these? Are we supposed to read through SE proposals? If this is the case - are they guaranteed to be correct and updated when the language changes?

9 Likes