Lia Stratopoulos

I'm not 100% certain, but it seems to me that [this](https://github.com/boost-experimental/te/blob/master/include/boost/te.hpp#L28-L47) is using the so-called [C++ Type Loophole](https://alexpolt.github.io/type-loophole.html). Maybe clang and gcc have dropped support for it given that CWG...

@akoolenbourke Not sure if you're still interested in this issue but I've recently ported `await.hpp` and `impl/await.hpp` and thought I would share my findings here since I can't find a...

> Thats weird, still believe there should be a dedicated macro I agree, the Optional thing is a hacky workaround for now but I would want something like `EXPECT_THAT(something, testing::Expected(some_val))`...

Hey just bumping this because I ran into a similar issue, this time with using `expected` to store types with a `delete`d placement `new` operator. In my case this works...

@ycollet thanks for your work on this! Later today I will test locally as well and let you know if anything comes up

It seems that everything is set correctly in terms of using `_CURRENT_` flavors of all variables where appropriate. I am still experiencing a bizarre issue where CMake segfaults when entering...

I am on Ubuntu 16.04 operating in the Windows Substem for Linux on a Windows 10 machine. When invoking CMake through Windows an issue shows up in the same place...

Today I did some experimenting with continuous integration builds which run on a project at my work. I was able to determine that the CMake segfault issue appears to be...

Sorry just a quick update: - the project appears to build correctly with the changes on my feature/target_link branch (modulo an issue with an ARM build which I'll have to...