Kai Yan

The output might be too much I will just leave the top, others are saved in the file below the input command are `cmake --build . --config Release && copy...

I am currently using cuda11.0 and cuda 11.4 It seems new visual studio (16.10) have trouble building many cuda related thing

> > It seems new visual studio (16.10) have trouble building many cuda related thing > > Have you seen similar issues with the new version of MSVC on other...

Just find this problem appears also in the old visual studio and maybe not a bug? Here are some link that might be useful https://developercommunity.visualstudio.com/t/xutility-errors-compiling-asio-and-basic-source/631347 https://stackoverflow.com/questions/67732065/why-does-vs2019-pro-have-compile-errors-with-xutility-xmemory-and-atomic-when

During the cmake building, I have this warning (not sure if this is important: 

> I solved my Windows build problems (also CUDA 11 and VS 16.10) by changing > > ```cmake > if (NOT CMAKE_CUDA_COMPILER_VERSION VERSION_LESS 9.0) > if(CMAKE_CUDA_SIMULATE_VERSION VERSION_GREATER_EQUAL 19.10.25017) > set(CMAKE_CUDA14_STANDARD_COMPILE_OPTION...

I solve this issue by change it into is_trivially_copy_constructible in pipeline.h of tdd. I submited my pull request can see if this should be an issue.

Just a notice that the segment fault happens at `Thread::thread()->set_file_resolver(new FileResolver(*fs_backup));` in load_dict function, whenever it is called