As discussed in matrix. The rationale would be that this is useful for refactoring. We unfortunately can't emit custom warnings inside property macros. Otherwise I would prefer if the macro emitted a helpful warning.
Right now the macro emits one unreachable expression warning at the macro site if the enum is empty. Does this make sense to keep or should I silence it as well?
As discussed in matrix. The rationale would be that this is useful for refactoring. We unfortunately can't emit custom warnings inside property macros. Otherwise I would prefer if the macro emitted a helpful warning.
Right now the macro emits one
unreachable expressionwarning at the macro site if the enum is empty. Does this make sense to keep or should I silence it as well?