Herb Sutter

I think this has been answered (thanks @filipsajdak !). > Something I haven't seen addressed or talked about is how cppfront or the new cpp2 syntax will handle type casting...

Sorry for the lag on this: > The new implementation forbids having duplicated types on the variant type list - types must be unique. I had been deliberately supporting a...

@filipsajdak Thanks! Here's what I've done so far (see this commit: ec32963f1144174e39d4274ab72801cbc238c666) - For UFCS, I've added your suggested `_TEMPLATE` forms for `.template` emissions... this makes the examples like `v.emplace(1);`...

@filipsajdak No worries, your issues and PRs have been super helpful, including that they've exposed (and helped fix, including on this thread) some significant limitations. Much appreciated! I was just...

@jgarvin wrote: > I was curious to see if cpp2 improvements included iterator invalidation safety Not yet implemented, but planned. See this project's home page [README.md > 2015: Lifetime safety](https://github.com/hsutter/cppfront/#2015-lifetime-safety)...

@JohelEGP wrote: > The whole file is Cpp1 syntax. Yes, a .cpp2 file can be all today's syntax. That particular file was one of a series of demos that shows...

Thanks! General timing note (maybe I should paste/link this in a few other PRs/issues if this isn't visible enough): My responses will be delayed because of the Kona meeting next...

But quick ack on this thread: My current thought is to require `narrow` or `narrow_cast` (semantically or syntactically) for narrowing conversions, and is one of the things still to be...

Thanks, everyone. Now that I've had time to reread this thread, I see @filipsajdak narrowed (pun intended) this down to several suggestions, one of which is the one I was...

I strongly agree with user documentation... for example, I have a 10-page "Cpp2 for Cpp1 programmers" guide fully written, because to me a core adoption metric is "can a programmer...