Brad Chamberlain

I've taken the liberty of adding "user issue" here due to both Michael's connection to the previous issue and Bonnie's response.

I think a way to get 90% to a solution on this issue is to rewrite: ```chapel public use Foo; ``` into: ```sphinx .. include:: Foo.rst ``` in the sphinx...

It could also simply "inline" the documentation for `C_Lib` into the documentation for `Lib` as proposed in https://github.com/chapel-lang/chapel/issues/14601#issuecomment-1036798841. However, this wouldn't be so simple if only a subset of `C_Lib`...

Related, but also not/bigger: I haven't read through learnChapelInYMinutes in years, but have always wondered whether it's organized in a way that we as Chapel experts would introduce and teach...

PR #5277 makes an attempt to fix this issue using the new where clause fixes introduced in PR #5275 but is currently failing with three tests.

I hate to look a gift horse in the mouth (particularly one that I requested), but I wonder whether it's worse to support thse foldings only for ``, `=`, and...

An interesting question would be whether there's any way to have them automatically refer to / pull our current (or better, currently released) version of the file so that there...

I'm thinking less about breaking changes, and more about making the lesson better over time. I think there's plenty of room to improve it, but if improving it requires jumping...

@lydia-duncan / @jabraham17 : It may have been updated since this issue was opened, but unfortunately it's still not in sync with the version in our release. :'( I'm curious...

@lydia-duncan : Is the implication of your "Aww" that we should re-open this? Or we could add a new issue about updating the test again and/or creating a way to...