I've found these functions fairly useful during my Clojure days! You said in the last pull request that it took you some hijinks to get the project to build, how is it you did that? I'm still writing my tests via copying code into another project since this won't build hah.

partition produces an array of arrays, each containing n elements, each offset by step (optional). It also allows an optional padding array which will attempt to fill the last partition to n elements if short.

partitionAll allows the last partition to be less than n elements long without using padding elements.

partitionBy applies a condition to each element in array, splitting it each time the condition returns a new value.

Hi,

I have added a simple method to format numbers (Double, Int, Float) using a NSNumberFormatter saved as a class var in a new class ExSwiftFormatter because formatters are expensive to create.

Tell me if you are interested in this PR before merging, I will add doc and update the readme.

I have also added a NSNumberFormatter extension to set the formatter precision.

formatter.setPrecision(3)

instead of

formatter.minimumFractionDigits = 3
formatter.maximumFractionDigits = 3

var price:Double = 12356789.424
var formatter = ExSwiftFormatter.numberFormatter
formatter.numberStyle = .DecimalStyle
formatter.setPrecision(3)
price.format() // "12,356,789.424"

formatter.numberStyle = .CurrencyStyle
price.format() // "$12,356,789.424"

If you agree I would like to add other formatters and also unit converters

This needs to be turned into a method that transposes the array it's called on, but I can't figure out how to enforce that the array be composed of arrays, similar to how we enforce that an array be composed of Equatables when we call unique() on it. Any ideas?

Hey!

I added one method (both in Dictionary and Array) in order to count elements meeting a criteria.

Maybe the name is not the best (possible conflicts with count standard property), but I think the idea is worth

Thanks!

Swift3 tip, not a bug

This code give operator warning: "operator should not be with body"

infix operator =~ {} infix operator |~ {} infix operator .. {} infix operator <=> {}

Commenting/Removing brackets solve the warning.

change add to below works

public func add(seconds: Int = 0, minutes: Int = 0, hours: Int = 0, days: Int = 0, weeks: Int = 0, months: Int = 0, years: Int = 0) -> NSDate {
    var calendar = NSCalendar.currentCalendar()
    let version = floor(NSFoundationVersionNumber)
    if ( version <= NSFoundationVersionNumber_iOS_7_1 || version <= NSFoundationVersionNumber10_9_2  ) {
        var component = NSDateComponents()
        component.second = seconds
        component.minute = minutes
        component.hour = hours
        component.day = days + weeks * 7
        component.month = months
        component.year = years
        return calendar.dateByAddingComponents(component, toDate: self, options: nil)!
    }

    var date : NSDate! = calendar.dateByAddingUnit(.CalendarUnitSecond, value: seconds, toDate: self, options: nil)
    date = calendar.dateByAddingUnit(.CalendarUnitMinute, value: minutes, toDate: date, options: nil)
    date = calendar.dateByAddingUnit(.CalendarUnitDay, value: days, toDate: date, options: nil)
    date = calendar.dateByAddingUnit(.CalendarUnitHour, value: hours, toDate: date, options: nil)
    date = calendar.dateByAddingUnit(.CalendarUnitWeekOfMonth, value: weeks, toDate: date, options: nil)
    date = calendar.dateByAddingUnit(.CalendarUnitMonth, value: months, toDate: date, options: nil)
    date = calendar.dateByAddingUnit(.CalendarUnitYear, value: years, toDate: date, options: nil)
    return date
}

My project won't compile onXcode 6.1. It gives me a bunch of errors on the Array.swift in the methods declarations. (Extension of generic type 'Array' from a different module cannot provide public declarations)

Does anyone know what needs to be changed?

takeWhile and skipWhile allow taking or skipping array elements that meet a given condition.

(I'd rename skip to drop in order to match the function names of other languages but I'll leave that decision up to you)

[1, 2, 3, 4, 5, 2].takeWhile { $0 < 4 }
// → [1, 2, 3]

[1, 2, 3, 4, 5, 2].skipWhile { $0 < 4 }
// → [4, 5, 2]

@ayn thanks so much for creating a fork that works on later versions of Swift, but unfortunately I get lots of errors, like "availability has been replaced with available", any ideas?

As a developer becomes familiar with Swift, they will likely find it strange that Apple would provide optional accessors on all of their data structures (which play nicely with the "if let" idiom), with the singular exception of Array.

Instead of being able to do this:

if let foo = array[3]
{
    // do something with foo
}

Instead you have to do something which feels clumsy in comparison:

if array.count > 3
{
    let foo = array[3]!
    // do something with foo
}

Writing an optional accessor seems a very obvious thing to do, to make Array fit better with the style of the rest of the language.

So I was quite shocked to discover that your "get()" method automatically wraps an out-of-bounds index, and that this behavior was intentional. I'm just having trouble wrapping my head around it.

Who would expect out-of-bounds index wrapping to be the default behavior of a method named "get()"?

If someone needed the (somewhat uncommon) behavior of out-of-bounds index wrapping, why would they want to hide that implementation detail behind a method call, instead of doing something explicit which calls better attention to it, like "array.get(index % array.count)"?

If they insist on hiding the behavior behind a method call, why wouldn't they choose a method name which at least hints at the behavior, like maybe .wrappedGet()?

This behavior and this method name just don't belong together.

Hi,

I have added getters to NSDate. Now you can do:

let date = NSDate()
let year = date.year

instead of

let date = NSDate()
let calendar = NSCalendar.currentCalendar()
let components = calendar.components(.CalendarUnitYear, fromDate: date)
let year = components.year

I have also added Comparison operator: <, <=, >, >=, == and updated the docs and README.md

I know this is no longer maintained, but just submitting this PR so others can try my swift 3 branch if you need this stuff to continue to work. I’ll push to my branch if I have more fixes.

This pull requests corrects the spelling of CocoaPods 🤓 https://github.com/CocoaPods/shared_resources/tree/master/media

One day I’ll make a bot that looks through the READMEs of all Pods, looks to see if it uses “Cocoapods” and PRs “CocoaPods” :D

— Ørta (@orta) February 10, 2016

Well lately I've been reading a book about smalltalk, and I find its object oriented boolean class very impressive, and it's the truly object oriented way to handle conditionals. A sample of smalltalk's conditionals is show below:

aBoolean
ifTrue: [someCode]
ifFalse: [otherCode]

In swift, the syntax can be something like this:

aBooolean.ifTrue{

}.ifFalse{

}

I tried to implement this in a C# library I am working on, but the language of C# has limitations on closure that you have to pass closure with syntax ifTrue(() => {}), rather than just ifTrue{}, which is a bit inconvenient. In Smalltalk, I know that it's possible to remove the parenthesis and arrow sign if closure is the last parameter in a function/method, which is very neat.

So what do you think? Will you consider implementing the extension methods ifTrue{} and ifFalse{} for boolean?

Hi, in NSArray.swift class there's a problem due to swift update. In fact in flatten function says "reflect is unavailable: call the Mirror(reflecting: ) initializer"