We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Most of the NextFaze projects that import FazeKit also import NFAllocInit just because FazeKit is incomplete.
Pros:
Cons:
The third option is my where I'd personally like to take it. @ricsantos @SilkyPantsDan ?
The text was updated successfully, but these errors were encountered:
Well, Swift source stability has settled down now, so going forward I don't see too many changes needed to keep it up to date.
I prefer using NFAllocInit over FazeKit, not sure why, maybe because I'm more familiar with it's contents.
Option 4: Make FazeKit mixed source, and move all the NFAllocInit code over to it, and sunset NFAllocInit?
Sorry, something went wrong.
FazeKit is the future
No branches or pull requests
Most of the NextFaze projects that import FazeKit also import NFAllocInit just because FazeKit is incomplete.
Proposals
Make FazeKit feature parity with NFAllocInit, thus sunsetting NFAllocInit
Pros:
Cons:
Make NFAllocInit feature parity with FazeKit, thus sunsetting FazeKit
Pros:
Cons:
Strip any code from FazeKit that already exists in NFAllocInit
Pros:
Cons:
The third option is my where I'd personally like to take it.
@ricsantos @SilkyPantsDan ?
The text was updated successfully, but these errors were encountered: