Use case for the "const" condition type

Usage
1

Just curious if there was a particular use case in mind for the "const" type in a condition object? I’m struggling to see how it serves any useful purpose, especially given that it does not even support macro evaluation. Either you hard-code a value of true, in which case you may as well not have the condition at all, or you hard-code a value of false and the preset will never be enabled. About the only thing I can think of is if you want to temporarily force a condition to evaluate to a particular value while you are debugging something, but that seems like a strange thing to support in the formal schema. Am I missing something?

CC: @kyle.edwards

1 Like
2

Now I’ve also come into this and wondering what is the point of that. I don’t see any use cases.

3

I think I got it, it’s the same as if(false) or if(true), and it’s handy eg. in vcpkg patches, you can see it there a lot if you need to disable some code part in the build system but you don’t want to remove it entirely, eg. to avoid/minimize potential merge conflicts or to preserve code logic for fast lookup what’s up.