!lymvtcwDJ7ZA9Npq:lix.systems

Lix Development

431 Members
(Technical) development of Lix, the package manager, a Nix implementation. Please be mindful of ongoing technical conversations in this channel.142 Servers

You have reached the beginning of time (for this room).


SenderMessageTime
20 Nov 2025
@just1602:systemli.orgjust1602In the lix codebase, what is the best way to print a compile time warning?15:19:35
@qyriad:katesiria.orgQyriad just1602  printTaggedWarning or printWarning 15:50:28
@just1602:systemli.orgjust1602 But they only show up at runtime, and not at compile time. At least when I do just build I don't see those warning show up in the build log. 15:57:02
@qyriad:katesiria.orgQyriad oh you mean compilation of Lix itself? 16:09:19
@qyriad:katesiria.orgQyriad well there's #pragma warning, but for anything more complex you'll have to write a clang-tidy lint. luckily there are already clang-tidy lints in the codebase you can look at 16:10:09
@just1602:systemli.orgjust1602 I'll try #pragma warning, it's just for a one off. It's we print a deprecation warning at runtime, and eldritch horrors want a compile time warning when we hit the version we target for the removal 16:12:30
@just1602:systemli.orgjust1602 Qyriad: ok, #pragma message seems to do what I was looking for, #pragma warning was just giving an error that warning wasn't a valid pragma instead of displaying the text 16:18:24
@just1602:systemli.orgjust1602 Now I just need to know that is the value format of LIX_MAJOR to be able to do # if LIX_MAJOR >= 2.96 ? :D 16:18:59
@just1602:systemli.orgjust1602Is it 2_96, 296, some other format?16:19:23

Show newer messages


Back to Room ListRoom Version: 10