This principle is probably formalized or named by someone, but got bitten again by it: one should always make “no value” clearly separate from “zero/nil/empty/first enum value”. Specifically in C, enums should not use “0” as a valid value I’d be able to implement a new feature in fe... blog.timokoola.com

@a_seagull_story I am getting more careful even with (b). While I am usually going with NONE being zero, I try to figure out if NONE will always have the same code paths as ”uninitialized”. I try to figure if that is the case

@tkoola Sounds good to me. I like it when we have these kind of chats. :)