How to use fastcopy v3.053/24/2023 ![]() Institute of Aerodynamics and Chair of Fluid Mechanics Reply to this email directly or view it on GitHub You are receiving this because you are subscribed to this thread. Is that there is no one bottleneck (which could be easily fixed) but ratherĪll implementation is adding to the compilation times bit by bit. Therefore, it's even hard to be 100% sure that concepts emulation is However, concepts are also used for overloading, so it didn't work in theĮnd. On Tue, at 6:35 PM, Krzysztof Jusiak I was thinking of that too. I wouldn't expect compile times to be significantly Language wise modules + type-checking definitions look promising but at the Reduce compile-times enough to make them negligible (unless you are using Non-template base classes, and maybe there are some better tuple/type-listĪlgorithms that can be used, but I doubt that fixing any of these will Maybe there is some "low hanging code" that could be lifted into ![]() Add lambdas to the mix and notĮven offering a compiled component with explicit instantiations for common ![]() TU (without precompiled headers), and it requires a lot of template code toīe instantiated multiple times by every TU. It increasesĬompile times a lot because it requires a lot of code to be parsed in every The whole library is header only and mostly template only. I haven't profiled it yet, so I don't know what might a bottleneck but maybe there is a solution already? I tried precompiled headers and they seem to help a bit, but, definitely something can be done from code point of view. ![]() Nevertheless, compilation times on my project increased from 1.5 second to 9 seconds since I started using ranges library. The logic itself is not huge as it is around 150 lines. ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |