I am considering doing a nomicon docs push for the 2018 release, taking input on desired topics to add or reinforce. Also interested in any discussion of what should be in the nomicon vs the reference (originally the nomicon was written as a partial replacement for the reference, when it was a tire fire, but now the reference is coming together?)
NLL and Futures and/or all of async seem like good candidates. Someone already has a PR up to try to introduce NLL stuff into the nomicon, haven't reviewed it yet.
I am also tempted to add things like some "safe" superset of all the reference semantics y'all are considering
like the nasty "creating a reference asserts the memory is allocated" issue we have in BTreeMap
@Gankro I'll write a blog post soon on the aliasing/reference model stuff
it's coming along real nice :)
but none of it is normative yet. not sure if it has relevance for the nomicon.
@RalfJ are the concepts far enough along that they would be a good idea to discuss in the nomicon?
well that depends on your scope. my plan was a "call for help" where I ask people to throw their stuff at miri and see what sticks
maybe that works better this time than last year because we have miri in the playground
I think the general concepts are a useful way to think about the rules for references. some of the details might change because we might need special exceptions for a thing or because we can factor away a special exception. but whether the concepts will be what we eventually make normative? no way to know^^