# Complete checking with an incorrectly-annotated init conformance?

**URL:** <https://forums.swift.org/t/complete-checking-with-an-incorrectly-annotated-init-conformance/69955>\
**Category:** Using Swift\
**Tags:** concurrency\
**Created:** [February 10, 2024, 12:52pm UTC](https://forums.swift.org/t/complete-checking-with-an-incorrectly-annotated-init-conformance/69955 "2024-02-10T12:52:47Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![mattie](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/mattie/32/13267_2.png) [@mattie](https://forums.swift.org/u/mattie)\
**Post date:** [February 10, 2024, 4:14pm UTC](https://forums.swift.org/t/complete-checking-with-an-incorrectly-annotated-init-conformance/69955/3 "2024-02-10T16:14:45Z")

</div>

> [@wadetregaskis](#):
>
> Note that the compiler is still going to warn you that the isolated `init` cannot satisfy the protocol's requirements (although in Swift 5.9.2, at least, it still _does_ - this will surely break in Swift 6… though oddly, in 5.9.2 with 'complete' concurrency checking it still does not).

I had to edit the original post because I over-simplified the problem. Sorry about that!

However, I'm not certain it's even worthwhile checking these kinds of things with anything less than a 5.10 compiler. In fact, I _thought_ had a solution to this problem with 5.9.2, but 5.10 made it harder!

---

_[View the full topic](https://forums.swift.org/t/complete-checking-with-an-incorrectly-annotated-init-conformance/69955)._
