Re: [boost] Release Managers: permission to merge small feature to release?

Subject: Re: [boost] Release Managers: permission to merge small feature to release?
From: Eric Niebler (eric_at_[hidden])
Date: 2012-12-29 02:07:38

On 12/28/2012 1:51 PM, Marshall Clow wrote:
> On Dec 28, 2012, at 4:50 AM, Daniel James <dnljms_at_[hidden]> wrote:
> 
>> On 27 December 2012 21:54, Marshall Clow <mclow.lists_at_[hidden]> wrote:
>>> I have a ticket <https://svn.boost.org/trac/boost/ticket/7652> asking for compile-time checked access to elements of a boost::array.
>>>
>>> I have implemented a specialization of boost::get (and for c++11, std::get) that does this, and it's been on the trunk and being tested for a couple weeks.
>>>
>>> This is technically not a bug fix, but new functionality, but I'd like to get it into the next release.
>>>
>>> So, I'm asking permission to merge to release.
>>>
>>> The change lists are 82083 (for the functionality), 82084 and 82102 (for the tests), and 82103 (for the docs)
>>
>> Some of those revision numbers are wrong.
> 
> Crud. 
> Apparently copy and paste is beyond my mental abilities.
> 	82083 (for the functionality)
> 	82089 and 82102 (for the tests)
> 	82105 (for the docs)
> 
>> Also, I don't like the idea of adding anything to 'std' at this stage.
> 
> I'm not adding stuff to "namespace std", but rather specializing a template function for boost::array that is already defined.
> But if you think that this is too late/risky to be added to this release, I'm OK with that.

<looks>

No, you're not specializing a function template. You're adding an
overload. My standardese is rusty, but I don't think that's allowed in
namespace std. Anyway, I'm with Daniel. Marshall, can you please hold
this change?

-- 
Eric Niebler
BoostPro Computing
http://www.boostpro.com