On Thu, 28 Jun 2018 at 12:49, Jonathan Wakely wrote:
> Yes, please report it to our bugzilla.
Ah, I've just seen https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86342 - thanks!
On Thu, 28 Jun 2018 at 12:32, Csaba Raduly wrote:
>
> On Wed, Jun 27, 2018 at 1:28 PM, Jonathan Wakely wrote:
> > Your mail is off-topic on this list, it would be appropriate on the
> > gcc-help list, or in Bugzilla if you want to report a bug.
> >
> >
> > On Wed, 27 Jun 2018 at 11:27, Csaba Raduly
On Wed, Jun 27, 2018 at 1:28 PM, Jonathan Wakely wrote:
> Your mail is off-topic on this list, it would be appropriate on the
> gcc-help list, or in Bugzilla if you want to report a bug.
>
>
> On Wed, 27 Jun 2018 at 11:27, Csaba Raduly wrote:
(snip)
>> 1. Why is a warning emitted only for the const
Your mail is off-topic on this list, it would be appropriate on the
gcc-help list, or in Bugzilla if you want to report a bug.
On Wed, 27 Jun 2018 at 11:27, Csaba Raduly wrote:
>
> #include
> #include
> #include
>
> using srange = boost::sub_range;
>
> void func(srange) // by value
> {}
>
> in
#include
#include
#include
using srange = boost::sub_range;
void func(srange) // by value
{}
int main()
{
std::string kitty{"meow"};
srange hello{kitty};
srange const& helref = hello;
func(hello);
func(helref); // line 17
return 0;
}
$ g++ -v
gcc version 9.0.0 2018
