Mateusz Pusz

Results 651 comments of Mateusz Pusz

> How about something like this? Smaller plus signs or small caliper handle gets totally unreadable when we deal with a small logo or favicon.

> While it's too bad to lose the "calipers" idea, I like the new logo a lot better! @chiphogg, which one? With or without the background?

> Even if arbitrary, I think it'd be nice to preserve the three shades in the background in their same shape and orientation: ![cpp_logo](https://private-user-images.githubusercontent.com/21071787/294228916-0b76c540-1865-457a-9924-56b8d40743a9.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MDQzODU1MzQsIm5iZiI6MTcwNDM4NTIzNCwicGF0aCI6Ii8yMTA3MTc4Ny8yOTQyMjg5MTYtMGI3NmM1NDAtMTg2NS00NTdhLTk5MjQtNTZiOGQ0MDc0M2E5LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDAxMDQlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwMTA0VDE2MjAzNFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTM4Yjg2ZDY5ZDUxNmFlOGVlMjc3ZDIxMDQ3YjhiZjIyNmY4NjdhNjNhZmY3ZTMwNmVmODMwNGRlOTZkNTY2NTImWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.3CvzIcWCwqOsuANzPvV1i-UB__pLko_9TSa02T24mcM) If those colors do not match...

> I think I prefer the version with the background overall. Here are also screenshots from the docs for both cases: ![image](https://github.com/mpusz/mp-units/assets/506260/661cbc7b-53d2-4992-8d66-f54ab70cde6d) ![image](https://github.com/mpusz/mp-units/assets/506260/2b942a33-d7d5-41d5-aa37-5232e2b8cbb9) Check both the logo and favicon.

> While it's too bad to lose the "calipers" idea, I like the new logo a lot better! Yes, the caliper or micrometer was a nice idea, but it did...

> use a user cmake toolchain file and specify it in the conan profile This has some issues. For example, the gdb debugger in VSCode may not know what the...

I think that @memsharded should answer those.

This is not the only overload participating in the overload resolution. The compiler can't choose the correct one because `static_assert()` aborts the instantiation of an invalid overload.

BTW, there are many other similar problems like that with this library. We have to meet at some point and work together to try to resolve those. Until then I...

I understand, but I can't provide it now as my code base is not stable. When it is on the mainline, I will provide one. In the meantime, here is...