Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[SR-6943] Expression was too complex to be solved in reasonable time; consider breaking up the expression into distinct sub-expressions error regression when trying to build with Xcode 9.3 beta #49491

Closed
pitiphong-p opened this issue Feb 7, 2018 · 4 comments
Closed

[SR-6943] Expression was too complex to be solved in reasonable time; consider breaking up the expression into distinct sub-expressions error regression when trying to build with Xcode 9.3 beta #49491

pitiphong-p opened this issue Feb 7, 2018 · 4 comments
Assignees
@xedin
Labels
bug A deviation from expected or documented behavior. Also: expected but undesirable behavior. compiler The Swift compiler in itself regression swift 4.1 type checker Area → compiler: Semantic analysis

Comments

@pitiphong-p
Copy link
Contributor

Previous ID SR-6943
Radar rdar://problem/37316308
Original Reporter @pitiphong-p
Type Bug
Status Resolved
Resolution Done

Attachment: Download

Environment

Xcode 9.3 beta 1 & 2, macOS 10.13.3

Additional Detail from JIRA
Votes 0
Component/s Compiler
Labels Bug, 4.1Regression, TypeChecker
Assignee @xedin
Priority Medium

md5: b4a7bd5d5c461d567626e4df37a4e043

Issue Description:

I have an project which is built fine in Xcode 9.2. However when I try to build it with Xcode 9.3 beta, there is an `Expression was too complex to be solved in reasonable time; consider breaking up the expression into distinct sub-expressions` error occur.

The expression that cause this error has some sub-expressions which may result the problem. It includes getting a value from the nested property of a Generic Constrained type and some expressions around severals operators

I attached a sample project which can reproduce the problem. However since I saw this error on the code which related to 3rd party library so it need to be run some command which I wrote the instructions in the `README.md` file

Please note that the same code was built successfully on Xcode 9.2 so I think this is a regression over Xcode 9.3 beta and Swift 4.1 compiler
@belkadan
Copy link
Contributor

belkadan commented Feb 7, 2018

Thanks, Pitiphong!

@swift-ci create

@xedin
Copy link
Member

xedin commented Feb 9, 2018

@pitiphong-p Can you please use the latest nightly toolchain of 4.1 to verify? I think it got fixed by #14322

@pitiphong-p
Copy link
Contributor Author

@xedin Confirmed. It works on the latest Swift Toolchain 2018-02-08. Thank you

@xedin
Copy link
Member

xedin commented Feb 10, 2018

Thank you, @pitiphong-p! Can you please resolve this issue?

@swift-ci swift-ci transferred this issue from apple/swift-issues Apr 25, 2022
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@xedin xedin

Labels
bug A deviation from expected or documented behavior. Also: expected but undesirable behavior. compiler The Swift compiler in itself regression swift 4.1 type checker Area → compiler: Semantic analysis
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@xedin @pitiphong-p @belkadan @AnthonyLatsis