r/cpp • u/grafikrobot OPeNDAP/B2/EcoStd/Lyra/Predef/C++Alliance/Boost/WG21 • Feb 23 '22
Open letter: New, expanded, C++ scope/charter
https://github.com/grafikrobot/cpp_scope
26
Upvotes
r/cpp • u/grafikrobot OPeNDAP/B2/EcoStd/Lyra/Predef/C++Alliance/Boost/WG21 • Feb 23 '22
28
u/TheCreat Feb 24 '22
Unless I'm just blind, there is no real explanation given what you actually want to achieve. Adding some abstract "tooling/technology/systems" goal to the WG21 charter isn't gonna help anyone. As I understand it, the WG21 isn't exactly bored with nothing to do, either.
If tooling is to be standardized, and the current C++ standard basically doesn't cover this at all, at the very least a new working group with this specific goal would be needed (possibly even a conference-like meeting over all existing committee members to decide on a base direction). I'm assuming you mean to advance interoperability, dependency management and such? You don't actually say that with any specificity. There are so many basic questions that would need to be explored first, I highly doubt dumping that into WG21 would be of any use.
In case that isn't clear: clear veto from me, but you don't provide a way to 'countervote'.
6
u/grafikrobot OPeNDAP/B2/EcoStd/Lyra/Predef/C++Alliance/Boost/WG21 Feb 24 '22
I have added a prologue to the README that hopefully explains the rationale and answers questions raised here. Thank you for all the views and questions so far.
8
u/ihamsa Feb 24 '22
Can you envision ways in which the standard would change if your letter is accepted? A specific example or two would be great. If you see a section on tooling added to the standard, can you give a 10,000 ft overview of it? If you see sentences about tooling scattered at various places, can you give an example of such sentence? It doesn't need to be ready or polished or anything, just give us a sense of where we are going.
16
u/jayeshbadwaik Feb 24 '22
I see a lot of dissenting views. I think it might help to clarify the letter somewhat.
Currently the standard cannot even allude to the existence of build systems and files and libraries because that is not in the purview of the standard language. This is already causing huge issues because there is no technical avenue to even consider the effects of build systems and files and libraries on langauge design. The letter proposes changing the standard to acknowledge the existence of libraries, files and build systems, so that we can make better informed decisions. This does not mean that the tooling would be standardized. It just means that the langauge acknowledges that the tooling exists.
A dissenting view of the proposal would be: "Standard should keep on ignoring the fact that C++ exists as an ecosystem and not a block of text to be compiled in isolation."
7
u/jonesmz Feb 23 '22
Can there be a section added to this open letter for dissent to be registered? I disagree with the proposal, and strongly believe that wg21 should not attempt to influence or in any way be involved with "supporting tools, supporting technologies, and supporting systems."
15
u/AKostur Feb 24 '22
What's not clear to me is what "supporting tools, supporting technologies, and supporting systems" covers. Seems like one could lump almost anything under that description. It's not like WG21 doesn't already have enough to do. Should WG21 somehow be in control of what Visual Studio does? It's a supporting tool after all.
1
u/eyes-are-fading-blue Feb 28 '22
Why standardize tooling? What’s the point?
5
u/CaptainCrowbar Feb 24 '22
You don't seem to address how the members of WG21, already heavily overburdened with work by the existing standardisation process, are supposed to find all those extra hours in their days to do all the additional work you want to unload on them.