My stackoverflow question was closed so here's a blog post about CoreWCF

> and was instantly downvoted and then voted to closed.

The outstanding vote to close is on the grounds of "needs details or clarity". Based on the comment that was left, I assume that the other party doesn't understand why you are asking a question, because it comes across that your motivation for asking is that you don't understand what to do, but it also comes across that the error message is already telling you exactly what to do.

If you have a different question - for example, why you should have to do the thing being suggested, or you don't understand how to do the thing being described - then you should edit the question to clarify that. With this clarification, it may be that your question is identified as a duplicate (of a more general question regarding why such "inherited conformance" must be restated in Swift, or what that means, etc.). I don't know Swift, so I can't advise there - I can only rely on my general understanding of programming languages in this general syntax family.

Regardless, the question would be improved by a proper minimal reproducible example (https://stackoverflow.com/help/minimal-reproducible-example). Minimal is a key component of this; please proactively try to remove irrelevant parts of the code example, so that you show only what directly causes the reported problem. This helps (https://meta.stackoverflow.com/questions/333952) other people understand and recognize the question - not just people who might answer it, but other people who have the same question who are looking for an existing Q&A.

> There's no hits on the warning I was getting.

I guess you mean that you tried searching for the warning and came up empty handed. I'm not sure why this happened for you. If I try copying and pasting into a search engine - e.g. https://duckduckgo.com/?q=Class+must+restate+inherited+%27Cl... - I get seemingly useful results off the top - including issues in the GitHub repository for Swift itself, such as one proposing and automatic "fix-it" for this error (I assume this concept is meaningful to Swift developers generally). I also see official Apple documentation at https://developer.apple.com/documentation/swift/sendable , several blog posts talking about the use of `@unchecked Sendable` with fully worked examples, etc.

> I do not think this question was worth downvoting or closing. People on SO nowadays seem way too eager to downvote and close.

Nobody ever thinks their own questions are worth downvoting or closure - they wouldn't ask if they did. But the standards aren't set by the OP; they're set by policy and surrounding discussion such as https://meta.stackoverflow.com/questions/417476 and https://meta.stackoverflow.com/questions/252677 and https://stackoverflow.com/help/closed-questions and https://stackoverflow.com/help/why-vote and https://meta.stackoverflow.com/questions/429808. And they're set this way because the site isn't about answering your question in the moment; it's about building up a searchable, useful repository of high quality questions and answers.