[type_traits] Time to merge Version 2 to the master branch?
Hi, Once Boost 1.59 is out, I'd like to suggest merging TypeTraits V2 to the master branch. It's a great job that will reduce boost library dependencies. Any chance this can happen soon? Best, Ion
Once Boost 1.59 is out, I'd like to suggest merging TypeTraits V2 to the master branch. It's a great job that will reduce boost library dependencies. Any chance this can happen soon?
I was about to ask about this - 1.59 is out now, so I see no reason not to merge. However, I do need to double check whether there are any critical patches to other libraries that haven't been merged to master yet. Are there any showstoppers for anyone else? John.
On 9/9/2015 12:09 PM, John Maddock wrote:
Once Boost 1.59 is out, I'd like to suggest merging TypeTraits V2 to the master branch. It's a great job that will reduce boost library dependencies. Any chance this can happen soon?
I was about to ask about this - 1.59 is out now, so I see no reason not to merge. However, I do need to double check whether there are any critical patches to other libraries that haven't been merged to master yet. Are there any showstoppers for anyone else?
Boost.Python still has an outstanding PR which I created to remove the deprecated message. I do not think that the Boost.Python maintainer has looked at any of the PRs as yet. Maybe someone with admin access to Boost.Python can just review and merge that PR. It is " Remove unused deprecated header file #25".
I was about to ask about this - 1.59 is out now, so I see no reason not to merge. However, I do need to double check whether there are any critical patches to other libraries that haven't been merged to master yet. Are there any showstoppers for anyone else?
Boost.Python still has an outstanding PR which I created to remove the deprecated message. I do not think that the Boost.Python maintainer has looked at any of the PRs as yet. Maybe someone with admin access to Boost.Python can just review and merge that PR. It is " Remove unused deprecated header file #25".
I don't consider that one a showstopper - there were some changes required to get code to compile at all - mostly where libraries were relying on implicit #includes. John.
On 09/09/2015 17:59, John Maddock wrote:
I was about to ask about this - 1.59 is out now, so I see no reason not to merge. However, I do need to double check whether there are any critical patches to other libraries that haven't been merged to master yet. Are there any showstoppers for anyone else?
Boost.Python still has an outstanding PR which I created to remove the deprecated message. I do not think that the Boost.Python maintainer has looked at any of the PRs as yet. Maybe someone with admin access to Boost.Python can just review and merge that PR. It is " Remove unused deprecated header file #25".
I don't consider that one a showstopper - there were some changes required to get code to compile at all - mostly where libraries were relying on implicit #includes.
Never mind, looks like they're all in master now, unless there are objections I'll merge type_traits to master this weekend. John.
John Maddock <jz.maddock <at> googlemail.com> writes:
However, I do need to double check whether there are any critical patches to other libraries that haven't been merged to master yet. Are there any showstoppers for anyone else?
Graph is currently broken because your pull request hasn't been merged yet: https://github.com/boostorg/graph/pull/42
participants (4)
-
Edward Diener -
Ion Gaztañaga -
John Maddock -
Marcel Raad