Replace the uses of "local variable" with "[block] variable with automatic storage duration"

[frederick-vs-ja]

P1787R6 dropped the previous buggy uses and definition of term local variable. But there're many remaining use of local variable.

This PR removes the remaining occurences except for one "conceptual local variable" in a comment (which seems OK to me as we're not talking about real local variable).

Fixes #6617.

[jensmaurer]

I would prefer to replace the remaining uses of "local variable" with "[block] variable with automatic storage duration" for consistency, instead of reintroducing a term that CWG agreed to abolish.

[frederick-vs-ja]

I would prefer to replace the remaining uses of "local variable" with "[block] variable with automatic storage duration" for consistency, instead of reintroducing a term that CWG agreed to abolish.

Thanks. I'm now switching to this direction.

[FrankHB]

I would prefer to replace the remaining uses of "local variable" with "[block] variable with automatic storage duration" for consistency, instead of reintroducing a term that CWG agreed to abolish.

They are not equivalent. The term "local variable" has nothing to do with the storage duration at all, it is now just "block variable", not necessarily "with automatic storage duration"; although most use cases apparently imply this. And personally I don't like too many occurence of the lengthy "with automatic storage duration" phrase when the storage duration is contextually clear enough.

[jensmaurer]

@FrankHB , works for me; I haven't looked at the details. If we mean "block variable", we should say so. If we mean "with automatic storage duration", we also should say so.

[frederick-vs-ja]

And personally I don't like too many occurence of the lengthy "with automatic storage duration" phrase when the storage duration is contextually clear enough.

Yeah. I wish it's clear enough to suppose the automatic storage duration can be implied by not using static or thread_local in the library wording.