Re: Upcoming C++ standards meeting in Rapperswil, Switzerland

I agree with the sentiment in the write-up, that ideally beginner 2d graphics needs are better handled by improving library/packaging support, not by importing (and speccing??) an ancient library. For instance in JS, people are more likely to pull in a library (of many) to help with graphing,

Re: Upcoming C++ standards meeting in Rapperswil, Switzerland

Thanks for sharing that overview! Although I can see why there's a lot of resistance to adding a graphics library to the C++ standard, it seems to me like a good idea. Even though, yes, there are going to be better and faster libraries out there, it's also true that anyone looking to maximize

Re: Upcoming C++ standards meeting in Rapperswil, Switzerland

My blog post about what happened at this meeting is now live: https://botondballo.wordpress.com/2018/06/20/trip-report-c-standards-meeting-in-rapperswil-june-2018/ Cheers, Botond On Tue, May 22, 2018 at 6:35 PM, Botond Ballo wrote: > Hi everyone! > > The next meeting of the C++ Standards

Re: Upcoming C++ standards meeting in Rapperswil, Switzerland

The New checker features look really promising. Yes, more of this stuff in C++ is very welcome. On Wed, May 23, 2018 at 1:53 PM, Chris Peterson wrote: > On 2018-05-23 1:35 PM, Botond Ballo wrote: > >> There is also work being done in this area outside the formal >> standards process, in the

Re: Upcoming C++ standards meeting in Rapperswil, Switzerland

The continued work on the 2D GFx API as a C++ standard is concerning. Since we're sending a GFx engineer to the committee, and AFAIK we're not going to use such an API to build our GFx stack, the arguments against continued development seem very compelling: - there are no clear users or

Re: Upcoming C++ standards meeting in Rapperswil, Switzerland

On Wed, May 23, 2018 at 1:35 PM, Botond Ballo wrote: > On Wed, May 23, 2018 at 4:05 PM, Jet Villegas > wrote: > > I'd rather see the committee focus on things like object lifetime > management > > so we don't have to port everything to Rust just to get

Re: Upcoming C++ standards meeting in Rapperswil, Switzerland

On 2018-05-23 1:35 PM, Botond Ballo wrote: There is also work being done in this area outside the formal standards process, in the form of the C++ Core Guidelines [2] (some of which can be checked statically) and the accompanying Guideline Support Library [3], and in the form of Microsoft's

Re: Upcoming C++ standards meeting in Rapperswil, Switzerland

On Wed, May 23, 2018 at 4:05 PM, Jet Villegas wrote: > I'd rather see the committee focus on things like object lifetime management > so we don't have to port everything to Rust just to get basic memory safety > guarantees. How much leverage do we have to push on that? I

Upcoming C++ standards meeting in Rapperswil, Switzerland

Hi everyone! The next meeting of the C++ Standards Committee will be June 4-9 in Rapperswil, Switzerland. This is going to be a pivotal meeting, with go / no-go decisions expected for several highly-anticipated C++20 features, including a subset of Modules; Coroutines; Ranges; and "natural