Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
Nikolai Vazquez
@nvzqz
Thoughts?
Cihat Gündüz
@Dschee
Are there any breaking changes since 2.0?
Nikolai Vazquez
@nvzqz
A few such as renames
Cihat Gündüz
@Dschee
Well then, a 3.0 release seems a reasonable choice as far as I'm concerned
And adding another one once Swift 3 is out with some streamlining in 4.0 would be great, too of course
Nikolai Vazquez
@nvzqz
Since a lot of people are jumping on xcode 8 and swift 3, is backwards compatibility with swift 2 that important?
It makes the code harder to maintain since some things need to be separated. Sage is swift 2 and 3 compatible for example
Cihat Gündüz
@Dschee
I would simply drop Swift 2 support but that's also your choice to make
But not now, of course since there's a few weeks or months until official Swift 3 release
Nikolai Vazquez
@nvzqz
Two weeks I believe until there are no more breaking changes to swift 3 and they start discussion for swift 4
Cihat Gündüz
@Dschee
In FileKit 4.0 this shouldn't be a problem and there would still be version 3.x for Swift 2 support
That's right but I'm not sure if that also means it's gonna be released immediately. I can imagine they just want it to be ready for a release candidate to concentrate on performance.
But I'm not up-to-date on that, so I might be wrong
Nikolai Vazquez
@nvzqz
As well as compiler bug fixes and whatnot
Cihat Gündüz
@Dschee
Anyways, as I said, there's still 3.x around for Swift 2
Nikolai Vazquez
@nvzqz
Agreed
What's the status of nsfilemanager on Linux?
Cihat Gündüz
@Dschee
That was also the approach the guys from Alamofire took when updating from Swift 1.2 to 2.x
Nikolai Vazquez
@nvzqz
I want to support Linux however idk if the foundation API has been ported hey
Cihat Gündüz
@Dschee
No idea, someone else will now better than me
Nikolai Vazquez
@nvzqz
Yet*
Cihat Gündüz
@Dschee
Just click the "up" button on your keyboard to correct your last entry ;)
Nikolai Vazquez
@nvzqz
I'm on my phone so I can't
Cihat Gündüz
@Dschee
Ah, ok sorry then ^^
Nikolai Vazquez
@nvzqz
No problem
I also want to get continuous integration going with travis or another provider but my knowledge in that is limited
My first working attempt is with sage so it shouldn't be too difficult
Cihat Gündüz
@Dschee
Oh that's a good idea. I could never get it to work on travis since there is/was a limit to iOS projects there. But I'm using Bitrise on my project https://github.com/Flinesoft/BartyCrouch and it was easy to configure and works as expected.
Anyways, gotta go to sleep already, it's after 1 a.m. here in Germany ;)
Nikolai Vazquez
@nvzqz
I love the icon and design
Alright we'll continue this later
Cihat Gündüz
@Dschee
Oh thanks, always nice to hear that :)
yup, see ya! take care
Nikolai Vazquez
@nvzqz
Likewise!
Nikolai Vazquez
@nvzqz
Just pushed version 3
Will now start cleaning up and migrating to Swift 3 for version 4
Cihat Gündüz
@Dschee
:+1:
I've updated the README on my fork to clearly state it is deprecated and people should use the original project.
Nikolai Vazquez
@nvzqz
Ok great!
There's a lot of errors I need to sift through but I should have it done within the next few days
Just noticed that GitHub has this feature
Cihat Gündüz
@Dschee
Yeah, milestones are great, especially if you link multiple issues to be part of a milestone. Then you can even see the current state of progress made. :) :+1:
For example you could create an issue for every step you plan to do before official release of Version 4.0 and link them to be part of the milestone.
Nikolai Vazquez
@nvzqz
Yeah that's definitely a great idea and for sure how we should probably go about this
11k
@11k
i'm trying to scrape data from about 3k html files and spit it out into a csv using a swift script, but it's leaking memory like crazy and i suspect filekit is the culprit. can anyone give me any guidance?
11k
@11k
thanks. wrapping everything in an autoreleasepool block seemed to fix the issue, though.
Punita Ojha
@punitaojha
This message was deleted