You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
currently, autobahn-cpp announces to run on C++11 or higher. which is getting old. and newer C++ version have added/rectified quit a bit of the new shiny stuff (async, anonymous funs, type inference, ..) we might want to use.
I doubt that even 5 years from now, more than 20% of people writing production C++ codebases will be using C++20. You want them to cut off the vast majority of the userbase because there's a new shiny? This isn't Javascript.
You want them to cut off the vast majority of the userbase because there's a new shiny? This isn't Javascript.
nope, it's not=) I agree, C++ has a different userbase and systems, tools or applications often have constraints. yeah, so obviously the consequence is: we cannot make C++ 20 a mandatory minimum for the library itself. we still could have (some) examples that make use of C++ 20 .. just not within the library (I don't see how a selective/optional use of C++ 20 features within the library would make much sense ...).
currently, autobahn-cpp announces to run on C++11 or higher. which is getting old. and newer C++ version have added/rectified quit a bit of the new shiny stuff (async, anonymous funs, type inference, ..) we might want to use.
The text was updated successfully, but these errors were encountered: