> what's the reason to not declare the pin statically as either or? That for plenty uses cases, pins are not statically either or, but are switched at runtime.

> what's the reason to not declare the pin statically as either or? That for plenty uses cases, pins are not statically either or, but are switched at runtime. (and the article really fails IMHO by not showing that, because doing that while keeping compile-time checks is the hard part, and its limits would be really interesting)