[episode 17] Sample code not working for xcode 16 #160
Yusuke-Ishihara-sp
started this conversation in
General
Replies: 1 comment
-
Hi @Yusuke-Ishihara-sp, we do not update old code samples to the newest version of Swift. We think of them as frozen in time when the episode was recorded so that it matches the video. Some amount of work may need to be done to update them, but that will need to be done by you. If you want you could maintain your own repo of updated code samples and we could link to the repo from this one. But we don't plan on keeping these code samples up-to-date right now. Since this isn't an issue with the repo I am going to convert it to a discussion. Please feel free to continue the conversation over there! |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Old projects are no longer maintained?
I am watching all past episodes and doing experiments in my xcode environment (ver. 16.0).
The instruction lies in the README.md, but it seems not valid as it has been over 7 years from the last commit.
No such module 'Overture'
runtime errorerror: error while processing module import: import may have triggered a dylib import
error.I'd like to know if those old sample codes will no longer be maintained. Personally, as an newbie here in functional programming world, it will be helpful if every sample code works as expected in newer environments.
I am considering to take time to refactor those projects incompatible to latest environments.
Let me know if you would be welcome to the such contributions!
P.S
To make project work (at least make it run, but a few bugs remain...), I did the following.
env settings
fix
ep0017.xcworkspace
.General
section.13.7
both for Debug and Release. (the value is arbitrary for operation check)12.0
. Without this setting, an error occurred after run.import Styling_2_Sources
. It seems that by ticking "Build Active Scheme" box, import procedures may be settled in unexpected way under the food, which I haven't gone through to detail yet.Beta Was this translation helpful? Give feedback.
All reactions