alfC

Ok, I was wondering if that was an oversight. I was confused because because it was supported in Qi and even appears in one of Mike Caise examples of X3...

I think maintaining it minimal it is a good thing, and in fact it can be implemented by the user (as I tried to do). The only problem is that...

Seriously?, how is it possible to make use of the "$" character in C++ syntax? Thanks for the great work.

The same can be said about any `std::is_trivially_***` trait. Also, for reference, Boost.Hana doesn't seem to have this limitation: ``` static_assert(std::is_trivially_copyable{}); ```

On Wed, May 2, 2018 at 4:58 PM, Kohei Takahashi wrote: > > I have an concern what I want to confirm, following code is (or will be) > >...

There is a more utilitarian point of view. In practical context... Trivially copyable means "s1 = s2 has the same effect as std::memcpy(&s1, &s2, sizeof(S))" For `struct S` the `s1...

On Wed, May 2, 2018 at 8:26 PM, Kohei Takahashi wrote: > @alfC thanks. > > My answer as of today is "no", sometimes I use bfn::vector or std::tuple, >...

Looks like in C++11 is not that difficult to solve this issue. It seems to be simply necessary to not explicitly define the `operator=(tuple const&)`. The *natural* result for tuples...

Yes, I agree, although there maybe more natural ways to obtain this result. The other problem is that for the non-trivial case, *something* needs to be done to `operator=(tpl const&...

If EIGVAL is set you can see the output for the eigenvalues (and for different k-points). These values can be can be converted to approximations of delta functions (e.g. gaussians...