One more benefit to favor enums for booleans here.
When passing facts/intent solely through a generic true/false, and possible a single more or less well-named identifier, you have increased risk of multiple and differing interpretations of what the values mean:
Did 0 or 1 mean failure or success? did false mean that the file did not exist or that you are not allowed to access it?
By explicitly naming what your 'true' and 'false' cases mean, you _can_ lessen this risk. (Of course, you can still communicate badly both with booleans and with badly named enums.)
Also for return values for functions, you don't have an identifier name (not all acting functions share name with their "report-back").
Further, enums _may_ upgrade elegantly when you learn your boolean assumption had >2 cases.
I read about half of of submissions, I don't know if others also said all this already.
I read about half of of submissions, I don't know if others also said all this already.