| 17 Jul 2025 |
 Sergei Zimmerman (xokdvium) | Yeah, it should be part of clang-tools-extra alongside clang-tidy, but nixpkgs build doesn't seem to have it for some reason. | 13:30:31 |
| Sergei Zimmerman (xokdvium) | https://github.com/llvm/llvm-project/blob/main/clang-tools-extra/clang-tidy/tool/clang-tidy-diff.py | 13:31:00 |
 fzakaria | Clang-tidy bonanza!? | 17:41:18 |
| fzakaria | sweet -- the IWYU is what i'm really after. | 17:41:28 |
| fzakaria | Makes navigating the codebase way easier. | 17:41:34 |
| fzakaria | i'm going to try and take on another issue from FetchTree tonight and stream again... (I'm picking some easy ones for now) | 17:42:03 |
 Alyssa Ross | IWYU is difficult for portable programs like Nix | 19:28:52 |
| Alyssa Ross | Often the header something happens to be defined in for your platform isn't the one you should actually be including to be standards conformant and portable | 19:29:09 |
| Alyssa Ross | (If it's possible to exclude libc headers rthat would probably help) | 19:30:31 |
| 18 Jul 2025 |
| fzakaria | aren't we solving that with Nix ? | 02:45:02 |
| fzakaria | like... we own all the header up until glibc... there's nothing non-portable | 02:45:16 |
 emily | Nix runs on Linux and Darwin (and also to some extent FreeBSD, Windows, …) | 02:45:59 |
| emily | so system header portability is still a concern (and has broken the build in the past) | 02:46:26 |
| fzakaria | aren't those controlled by IFDEF macros so it's still IWYU..
anyways I don't think 100% is necessary | 02:54:29 |
| fzakaria | but something more than today; I open any file and 1/2 of every include is either unused as per clangd or there's no include so it's difficult to follow the hierarchy | 02:54:53 |
| fzakaria | like aspirational | 02:55:01 |
| fzakaria | :) | 02:55:02 |
| fzakaria | I found this bug in Nix -- I sent a failing test case to capture it
https://github.com/NixOS/nix/pull/13456
Dunno if we like having test cases that validate the failure mode -- albeit easy to flip | 02:56:26 |
| emily | Alyssa means that including system headers can non-portably lead to the definition of a symbol that is only properly (portably) obtained by including a header that a standard specifies it's found in | 03:23:19 |
| emily | because of nested includes in the system headers etc. | 03:23:25 |
| emily | at least a naive "redundant include checker" would complain about including both such headers, even if it is the correct thing for portability across platforms | 03:23:59 |
| fzakaria | sure; still better than current model. You can special case the 10% rather than give up on the 90% | 15:08:38 |
 Mic92 | In reply to @fzakaria:one.ems.host
sweet -- the IWYU is what i'm really after. You mean the clang-tidy one? Works quite well on nix-eval-jobs | 17:33:14 |
| Mic92 | In reply to @qyliss:fairydust.space
IWYU is difficult for portable programs like Nix Maybe that can be enabled somehow for nix header only? | 17:34:34 |
| Mic92 | Same actually for platform specific header - could be a bit tedious though | 17:35:25 |
| Mic92 | @xokdvium:matrix.org: clang format stuff is good to go? | 17:36:58 |
| Sergei Zimmerman (xokdvium) | I think so. The diff is good and the auto-rebase script seems to work well. | 17:37:33 |
| Mic92 | Okay. Hit it! | 17:38:04 |
| Sergei Zimmerman (xokdvium) | Done! No more range formatting. Yay! | 17:40:50 |
| Sergei Zimmerman (xokdvium) | Pinned an issue about the auto-rebase script: https://github.com/NixOS/nix/issues/13502 | 18:02:18 |
