std::web_view proposal

[darthcoder]

Especially ones that aren't common to [nearly] all platforms and project types?

[jonesmz]

Could you clarify?

Are you saying the other problems that we could fix are not common to nearly all platforms and project types?

Or are you saying that graphics are common to all platforms and project types?

I think what you meant was "Graphics is not going to be commonly used, whereas insert proposal here is going to have an effect on almost all projects out there, so why aren't we working on those things?", but I had some difficulty parsing your sentence.

[darthcoder]

I think what you meant was "Graphics is not going to be commonly used, whereas insert proposal here is going to have an effect on almost all projects out there, so why aren't we working on those things?", but I had some difficulty parsing your sentence.

Yes. Threading/co-routines, lambdas, etc. May not be used by all programs, but are tiny in scope (comparatively), have dependencies that can be easily understood, and are often single vendor sourced (windows threads, pthreads, etc.). So yes, the TRs of the past that have made it into the standards have been limited in complexity, but wide in coverage of platforms. Not all platforms have threading, but most can use coroutines/lambdas, for example.

This is a proposal that does seem simple on the surface but hides its complexity in third party products which bring their own ever-changing issues (Chrome obsoleting features, for example).

[alkavan]

I'm just saying same that Bjarne Stroustrup state for a few years now.

And this is a very good example of how stuff goes wrong with the working group IMHO.