Fixed: Swift error in file Archive+MemoryFile.swift #322
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
fixed : error: value of optional type 'UnsafeMutablePointer<FILE>?'
|
Hi Dirk, Thanks for making me aware of this. I just merge #323, which obsoletes |
|
Hey Thomas the dev branch builds without problems :) |
|
The project I am working on uses the main branch tho, when do you think this will be merged into that? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #320
Fixed this smal error occuring during building of the package :
Changes proposed in this PR
The proposed change in the MemoryFile class aims to address a build error related to the unwrapping of an optional value. The error message indicated that result, which is of the type UnsafeMutablePointer? (an optional pointer to a file), must be explicitly unwrapped before it can be used in the fseeko function call.