Can you explain your reasoning in more depth?

Even though Crystal follows the SemVer spec, it's not directly tied with each other to be in std. Also SemanticVersion probably has the least practical real world usage amongst stuff which were previously discussed to be removed from std like Markdown.

I think it's still useful as a macro feature.

Despite the name, the implementation isn't even specific to SemVer, but can even be used with different versioning schemes. So maybe it should be renamed?

But I don't see a reason to remove it, especially considering the implementation is pretty straightforward.

I also don't see a need to remove it, plus the macro to compare versions is very useful and without SemanticVersion it wouldn't be possible.

On a second thought, it does no harm to keep it 👍