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

0.9.0/0.9.1 don't build with Swift 5.0.x #217

Closed
1 task done
kengruven opened this issue Jun 12, 2020 · 4 comments
Closed
1 task done

0.9.0/0.9.1 don't build with Swift 5.0.x #217

kengruven opened this issue Jun 12, 2020 · 4 comments

Comments

@kengruven
Copy link
Collaborator

kengruven commented Jun 12, 2020

Please help prevent duplicate issues before submitting a new one:

  • I've searched other open/closed issues for duplicates before opening up this new issue.

Report

What did you do?

The Cartfile of my project used to have the line:

github "iwasrobbed/Down" == 0.8.6

I want to try out a feature that's in the 0.9.x series, and I see in the README that 0.9.2+ is for Swift 5.1 (which I don't have), so I changed this line to:

github "iwasrobbed/Down" == 0.9.1

and ran:

carthage update --no-use-binaries --platform Mac Down

What did you expect to happen?

I expected version 0.9.1 to be built, and to appear in Carthage/Build/Mac/Down.framework.

What happened instead?

I got a compilation error:

.../Carthage/Checkouts/Down/Source/AST/Styling/Stylers/DownStyler.swift:38:71: error: type of expression is ambiguous without more context
    private var listPrefixAttributes: [NSAttributedString.Key : Any] {[
                                                                      ^

Looking at the code, this appears to be using a new Swift 5.1 language feature, even though it was added to Down in the 5.0-compatible era (0.9.0 / 0.9.1).

How hard would it be to add one word (return) here?

@kengruven
Copy link
Collaborator Author

I forked and branched (from tag "v0.9.1") with 2 small changes, and this builds with Swift 5.0.1 again:

master...kengruven:swift50

@iwasrobbed
Copy link
Collaborator

Hi @kengruven 👋 You're welcome to maintain your fork, but I'd rather not backport changes to prior Swift versions. It's a rabbit hole that only benefits a few people versus the maintainers having to keep a mental model of all these extra changes

@kengruven
Copy link
Collaborator Author

That's fair. Can we at least update the README?

@iwasrobbed
Copy link
Collaborator

@kengruven Done here 296ad54

Thanks for pointing it out

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants