So I was starting to do a kind of "High-level Design Plan" background doc for the Chalk Integration meeting... except that I know I am repeating material from the rustc-guide. (I didn't get super far yet, was mostly "playing around" to try and decide what I want to include)
Maybe it's better to just point folks at the rustc-guide, except that at least some of the plans that @scalexm and I were discussing are ever-so-slightly different than what is there. But then again I feel like it's useful to have a kind of "outline" for what we would discuss in the meeting.
cc @tmandry, who was writing high-level docs as I recall.
I'll probably poke at it a bit more later and try to at least get the "outline" more in place
I think it could be healthy to continue iterating on how we talk about this stuff at a high level :)
in particular, knowing what "level" to write the rustc guide at has been somewhat of a challenge in the past, I'd say
and iterating within the existing structure is harder
that said, you could send people to the guide. my main worry would be that the traits chapter is just long
but I'm sure that cherry-picking the right sections would alleviate that
also, the content you have in the paper doc looks nice, it would be good to incorporate into the guide somehow