Re: [boost] [utility/result_of] decltype-based implementation breaking valid code on msvc-10
On 4/5/2010 6:05 PM, Daniel Walker wrote:
On Mon, Apr 5, 2010 at 6:39 PM, Eric Niebler<eric@boostpro.com> wrote:
https://svn.boost.org/trac/boost/ticket/4072
A patch is attached to the ticket. I've confirmed that it un-breaks proto on msvc-10, but have not tested it further.
Good catch. Seems reasonable to me. In general, if some vendor releases an inadequate std:result_of or decltype, it would be good to have boost::result_of as a functional fallback, which is yet another reason to resolve the lambda/result_of issue. Enabling lambda to support boost::result_of's signature protocol, as in ticket 864, would do the trick. That way msvc-10 users would be able to enjoy lambda/result_of compatibility, even if msvc-10 still has some wrinkles.
Daniel, I don't necessarily disagree, but I'm not really interested in getting this small issue mixed up with the larger issue of lambda/result_of compatibility. I just want result_of to work on msvc-10. -- Eric Niebler BoostPro Computing http://www.boostpro.com
On Mon, Apr 5, 2010 at 10:58 PM, Eric Niebler <eric@boostpro.com> wrote:
On 4/5/2010 6:05 PM, Daniel Walker wrote:
On Mon, Apr 5, 2010 at 6:39 PM, Eric Niebler<eric@boostpro.com> wrote:
https://svn.boost.org/trac/boost/ticket/4072
A patch is attached to the ticket. I've confirmed that it un-breaks proto on msvc-10, but have not tested it further.
Good catch. Seems reasonable to me. In general, if some vendor releases an inadequate std:result_of or decltype, it would be good to have boost::result_of as a functional fallback, which is yet another reason to resolve the lambda/result_of issue. Enabling lambda to support boost::result_of's signature protocol, as in ticket 864, would do the trick. That way msvc-10 users would be able to enjoy lambda/result_of compatibility, even if msvc-10 still has some wrinkles.
Daniel,
I don't necessarily disagree, but I'm not really interested in getting this small issue mixed up with the larger issue of lambda/result_of compatibility. I just want result_of to work on msvc-10.
Of course. I agree. One step at a time. If decltype doesn't work in msvc-10, then result_of shouldn't use decltype on msvc-10. Your patch looks fine to me. Daniel Walker
On 4/5/2010 8:30 PM, Daniel Walker wrote:
One step at a time. If decltype doesn't work in msvc-10, then result_of shouldn't use decltype on msvc-10. Your patch looks fine to me
Are you the maintainer of result_of? Or is it Doug? I notice utility/result_of doesn't have a maintainer listed in libs/maintainers.txt. -- Eric Niebler BoostPro Computing http://www.boostpro.com
On Tue, Apr 6, 2010 at 1:58 AM, Eric Niebler <eric@boostpro.com> wrote:
On 4/5/2010 8:30 PM, Daniel Walker wrote:
One step at a time. If decltype doesn't work in msvc-10, then result_of shouldn't use decltype on msvc-10. Your patch looks fine to me
Are you the maintainer of result_of? Or is it Doug? I notice utility/result_of doesn't have a maintainer listed in libs/maintainers.txt.
I'm not the maintainer, but if Doug is busy and you need someone I'd be glad to volunteer for the job. Daniel Walker
On Tue, Apr 6, 2010 at 5:33 AM, Daniel Walker <daniel.j.walker@gmail.com> wrote:
On Tue, Apr 6, 2010 at 1:58 AM, Eric Niebler <eric@boostpro.com> wrote:
On 4/5/2010 8:30 PM, Daniel Walker wrote:
One step at a time. If decltype doesn't work in msvc-10, then result_of shouldn't use decltype on msvc-10. Your patch looks fine to me
Are you the maintainer of result_of? Or is it Doug? I notice utility/result_of doesn't have a maintainer listed in libs/maintainers.txt.
I'm not the maintainer, but if Doug is busy and you need someone I'd be glad to volunteer for the job.
I am no longer useful as a maintainer. I would be thrilled for you to take over the maintainership of result_of. Thank you! - Doug
participants (3)
-
Daniel Walker -
Doug Gregor -
Eric Niebler