Mon, 01 Sep 2014 09:10:44 GMT

The following also used to work up to 1.55, and is now broken.

$ cat foo.cc
#include <string>
#include <boost/flyweight.hpp>
using string = boost::flyweight<std::string>;
void foo(string) {}
int main()
{
  foo({});
}
$ clang++-mp-3.5 -std=c++11 -I /opt/local/include foo.cc
foo.cc:10:3: error: no matching function for call to 'foo'
  foo({});
  ^~~
foo.cc:6:6: note: candidate function not viable: cannot convert initializer list argument to 'string' (aka 'flyweight<std::string>')
void foo(string) {}
     ^
1 error generated.
$ g++-mp-4.9 -std=c++11 -I /opt/local/include foo.cc
foo.cc: In function 'int main()':
foo.cc:10:9: error: converting to 'string {aka boost::flyweights::flyweight<std::basic_string<char> >}' from initializer list would use explicit constructor 'boost::flyweights::flyweight<T, Arg1, Arg2, Arg3, Arg4, Arg5>::flyweight(Args&& ...) [with Args = {}; T = std::basic_string<char>; Arg1 = boost::parameter::void_; Arg2 = boost::parameter::void_; Arg3 = boost::parameter::void_; Arg4 = boost::parameter::void_; Arg5 = boost::parameter::void_]'
   foo({});
         ^

status changed; resolution set

Joaquín M López Muñoz — Fri, 05 Sep 2014 10:12:08 GMT

status new → closed
resolution → fixed

Fixed at:

https://github.com/boostorg/flyweight/commit/20230d966942fa4bfddba3a2b8fea0cd26eee6d4

I'd appreciate if you could test the fix works for you.

Tue, 16 Sep 2014 13:30:40 GMT

Hi Joaquin,

Thanks for the quick fix. Yes, I can confirm that it fixed my issue. FWIW, I have also observe a 20% speed up of my parsing routines (from 1.55 to 1.56), that use flyweight for identifiers. Nice!

Boost C++ Libraries: Ticket #10439: Flyweight: now the constructor is explicit

status changed; resolution set