state of libstdcxx_so_7-branch

[Benjamin Kosnik]

> The question is whether to make a clean break now, or wait until 
> concepts come into the FSF tree. I'm leaning toward doing it now on the 
> cxx0x-branch. Then, ConceptGCC will be based on the cxx0x-branch, so it 
> will get all of the ABI-breaking changes from the libstdcxx_so_7 branch 
> and from the concepts changes. This would help me immensely, because it 
> means that my concepts changes won't always conflict with other changes 
> in libstdc++. Of course, you all need to decide whether that's in your 
> best interests, too.

We're both leaning the same way, it appears.

;)

I think we have converged upon the clear advantages of this approach:

1) keeping the library itself simple, or as simple as possible
2) keeping the maintainers sane

What is your merge/update plan WRT cxx0x-branch and mainline? Do you 
have a schedule, or a feeling, or what?

> Either way, we should always plan on moving the non-ABI-breaking 
> features from the cxx0x-branch to mainline. Long before we get concepts, 
> we'll still want to have library support for rvalue references, variadic 
> templates, etc. in mainline and under -std=c++0x.

Yes. We should still be pretty aggressive about keeping things in sync I 
think. We have to take pains to minimize divergence, since this is 
potentially a long-lived branch.

I think we want something stronger, actually: I think we should make 
every effort to make cxx0x and mainline testsuites match, at least on a 
file-per-file basis. (There will be some xfailing, etc.)

That way the merges only have to deal with the rest of this stuff.

-benjamin