I think this then runs up against the problem presented in the thread linked above where if somebody wanted to enforce this codebase-wide they would need to ban switching over non-exhaustive values (e.g. Int/String) whether the use of @unknown default is an error rather than a warning.