The compiler is unable to check that this switch is exhaustive in reasonable time

Question

The compiler is unable to check that this switch is exhaustive in reasonable time

achirkof opened this issue 5 years ago · comments

Hi! Got an issue trying to build app "The compiler is unable to check that this switch is exhaustive in reasonable time"

Probably need to add default value.

It works several days ago. Looks like updating fonts might be a cause of issue.

Thi Doan · Answer 1 · Wed Jul 10 2019 11:33:32 GMT+0800 (China Standard Time)

Thanks for reporting this. Would you mind to open a PR to fix it?

Lukáš Hromadník · Answer 2 · Wed Jul 10 2019 15:35:22 GMT+0800 (China Standard Time)

Can you please provide us with some information? Like hardware specs, Xcode version, library version and version of the Cocoapods?

I've just tried my test app on my very old Macbook 2012 and I'm not getting this error during the build nor the archivation.

Andrey Chirkov · Answer 3 · Wed Jul 10 2019 15:55:40 GMT+0800 (China Standard Time)

My laptop is:
MacBook Pro (Retina, 15-inch, Mid 2014)
Processor 2,5 GHz Intel Core i7
Memory 16 GB 1600 MHz DDR3
Xcode 11 beta 3 (11M362v)
FontAwesome.swift 1.8.1 (cocoapods)

I think it's specific for Xcode 11 error.

Benjamin Myers · Answer 4 · Wed Jul 31 2019 01:42:46 GMT+0800 (China Standard Time)

I compiled the code in Enum.swift and ran into no issues. Not sure if you fixed the issue in the weeks since the last comment, but it seems to me that everything runs fine with the switch statement.

Looks like it's an Xcode 11 issue.

-Ben

Model Name: MacBook Pro (2017)
Model Identifier: MacBookPro14,2
Processor Name: Intel Core i5
Xcode Version 10.2.1 (10E1001), Swift 5

Robert Crabtree · Answer 5 · Fri Aug 02 2019 09:19:50 GMT+0800 (China Standard Time)

I have the same issue with Xcode Version 11.0 beta 4. No problems with Xcode 10.3

Thi Doan · Answer 6 · Fri Aug 02 2019 10:19:41 GMT+0800 (China Standard Time)

Could you file a bug report to Apple?

Daniel Roble · Answer 7 · Sat Aug 03 2019 05:53:13 GMT+0800 (China Standard Time)

I have the same issue with Xcode Version 11.0 beta 3.

Phuah Yee Keat · Answer 8 · Sat Aug 03 2019 07:52:18 GMT+0800 (China Standard Time)

Same issue with Xcode 11 beta 5 as well.

Phuah Yee Keat · Answer 9 · Sat Aug 03 2019 08:41:50 GMT+0800 (China Standard Time)

Created a pull request
#222

Guillaume Bellut · Answer 10 · Sun Aug 11 2019 20:45:07 GMT+0800 (China Standard Time)

Could you file a bug report to Apple?

I don't think this is a bug. It looks like Xcode 11 is just being more restrictive on the enum switch to be able to compile faster.

Marc Ruiz · Answer 11 · Fri Aug 23 2019 21:17:52 GMT+0800 (China Standard Time)

Same issue with Xcode 11 beta 6 as well. I'm with @Tulleb , it seems they are getting more restrictive. However, as in this case switch is exhaustive... I'm not sure the compiler should complain about it.

Umut Can Alparslan · Answer 12 · Sun Aug 25 2019 18:33:55 GMT+0800 (China Standard Time)

I'm having the same problem. I'm using Xcode 11 beta 6.

Marc Ruiz · Answer 13 · Mon Sep 02 2019 19:50:14 GMT+0800 (China Standard Time)

This issue has been fixed with #222

gezamiklo · Answer 14 · Tue Sep 03 2019 18:37:52 GMT+0800 (China Standard Time)

The issue still persists. I understand that the switch is exhaustive, but cannot alter the compiler. Maybe in the final version it will compile. Who knows? I've unlocked the file and added a default case returning an empty string. If the final version still won't compile this, there are no other ways (if, else if would be a rude joke :D)