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
Subtree Split the Core #142
Comments
Isn't that what typelift/Basis is for? |
No. I'm going to leave the Basis around as an exploration of pure declarative programming in Swift rather than just FP idioms like we're doing here. I will mark it as such. The code it produces is horrendously inefficient but tremendously beautiful. Such a creature cannot be allowed to ship... The Core at this point is Box, Result, Either, List, the operator sections, and some combinators and I would like to see it removed from Swiftz so we can focus on higher abstractions and instances instead of rudimentary data structures. |
How about "SwiftX", then? |
Reminds me too much of my poor Swift-Extras :) Spitballing Here:
|
How about TLKit, if we want that style of name? |
Or
|
... CoreData seems like a bad choice. |
@pthariensflame |
OK. Let's a least offer 3 of our favorites so we can narrow the field. No decisions yet: For me it's
|
Of those, three, I favor |
@pthariensflame Do you have two more suggestions picked out? |
I think I already suggested SwiftX, but I could also maybe get behind SwiftFP, or TLCore, or most anything of those patterns. |
CoreFP maybe (punning CoreFoundation)... I'm starting to warm to that kind of name. +1 SwiftX too. Implies we're just extending the STL rather than throwing in a bunch of new stuff like Swiftz does. |
💡 How about a different stylization of SwiftX? As in Swiftx. If you want full Swiftz, you just move over a key :) |
Swiftx is perfect! |
Then. Tonight's the night. |
Finished. |
Related to #118
I think with #131 it's high time the core became its own µFramework and possibly get a name change.
Thoughts, ideas, names, cash, I'll take them all.
The text was updated successfully, but these errors were encountered: