Too many cases in path enum #3219
Replies: 1 comment
-
Hi @jaanussiim, I'm sorry you are running into issues, but also I'm not really sure there is much we can do about this. No matter what there are always going to be limitations of what Swift can handle. An enum with 105 cases is quite extreme, and if Swift is having problems with it I'm not sure there is much we can do. We do have some plans in the future that will help eliminate some stack frames from highly composed features, but even then you will still be able to run into the problem if you add even more cases to your enum. I'd highly recommend simplifying this domain. Are all 105 features truly distinct from each other, or could some perhaps be combined and hold onto configuration state that controls their behavior? And if all 105 features are truly distinct, then you may need to just not use our stack navigation tools. You may be better off just using a vanilla Another idea that comes to mind is to mark the I am going to convert this to a discussion because there really isn't much we can do in the near term about this. |
Beta Was this translation helpful? Give feedback.
-
Description
This is related to following discussion #3162
Currently in my project, have to run in release mode on local device while developing.
Sample code to reproduce the issue
Checklist
main
branch of this package.Expected behavior
No response
Actual behavior
No response
Steps to reproduce
No response
The Composable Architecture version information
1.11.2
Destination operating system
17.5.1
Xcode version information
15.4
Swift Compiler version information
No response
Beta Was this translation helpful? Give feedback.
All reactions