Re: [patch] fix libstdc++/57336

2013-05-21 Thread Jonathan Wakely
On 21 May 2013 09:24, Daniel Krügler wrote: > 2013/5/21 Jonathan Wakely : >> This broke due to some front end changes that disallow forming >> function types that return abstract types. std::reference_wrapper >> always passes an lvalue reference to __invoke so it's correct to use >> an lvalue refe

Re: [patch] fix libstdc++/57336

2013-05-21 Thread Daniel Krügler
2013/5/21 Jonathan Wakely : > This broke due to some front end changes that disallow forming > function types that return abstract types. std::reference_wrapper > always passes an lvalue reference to __invoke so it's correct to use > an lvalue reference as the result_of's template argument. I agr

Re: [patch] fix libstdc++/57336

2013-05-21 Thread Jakub Jelinek
On Tue, May 21, 2013 at 09:18:15AM +0100, Jonathan Wakely wrote: > This broke due to some front end changes that disallow forming > function types that return abstract types. std::reference_wrapper > always passes an lvalue reference to __invoke so it's correct to use > an lvalue reference as the

[patch] fix libstdc++/57336

2013-05-21 Thread Jonathan Wakely
This broke due to some front end changes that disallow forming function types that return abstract types. std::reference_wrapper always passes an lvalue reference to __invoke so it's correct to use an lvalue reference as the result_of's template argument. PR libstdc++/57336 * incl