Bug in Swift regarding non public resultBuilders in public init?

Sajjon · October 25, 2022, 10:46am

I just hit a strange compilation error I have not seen before using a public init, which in turn used a non-public ResultBuilder - this was an error on my part. However, Swift actually compiled this. I believe this to be a bug, since if I declared any type, e.g. a struct as internal and try to that type in a public init, Swift will produce a compilation error. But it did not for a non public ResultBuilder.

In another package I tried to use this public init which uses the non public ResultBuilder, and the compiler produced this compilation error:

github.com

apple/swift/blob/414ef860a688b20d15a6fb03f92ba3abc88226fa/include/swift/AST/DiagnosticsSema.def#L6364-L6368


      
          ERROR(result_builder_missing_available_buildpartialblock, none,
                "result builder %0 does not implement any 'buildBlock' or a combination "
                "of 'buildPartialBlock(first:)' and "
                "'buildPartialBlock(accumulated:next:)' with sufficient availability for "
                "this call site", (Type))

And googling the error swift "with sufficient availability for this call site" gives no result other than Swift repo, so seems like not many people have seen this error.

marcocarnevali · January 18, 2023, 1:11pm

I had the same problem today. As expected the LogBuilder needs to be public if accessed outside of its own domain. This make sense but probably the compiler needs an improvement so that it can detect which is the real issue here.