Bruce Merry 46dbee7d42 Avoid explicitly resetting a std::[experimental::]optional
Now that #851 has removed all multiple uses of a caster, it can just use
the default-constructed value with needing a reset. This fixes two
issues:

1. With std::experimental::optional (at least under GCC 5.4), the `= {}`
would construct an instance of the optional type and then move-assign
it, which fails if the value type isn't move-assignable.

2. With older versions of Boost, the `= {}` could fail because it is
ambiguous, allowing construction of either `boost::none` or the value
type.
2017-05-27 23:52:23 +02:00
..
2017-03-10 15:42:42 +01:00
2017-01-31 17:28:29 +01:00
2017-01-31 17:05:44 +01:00
2017-03-10 15:42:42 +01:00
2017-04-08 23:25:13 -04:00
2016-12-16 15:00:46 +01:00
2016-12-16 15:00:46 +01:00