`init(capacity:)` on RangeReplaceableCollection

[lancep (Lance Parker)]

+1 for init(minimumCapacity:)

[benrimmington]

@jrose

I've been going the other direction when this has come up in the last few months: there is nothing useful you can do from knowing the current capacity, and so it doesn't make any sense to expose it. Just call reserveCapacity .

When an array/dictionary/set is used as an NSCache alternative, you might want to evict old elements when count == capacity.

But this cache limit could be stored elsewhere, and capacity doesn't need to be a protocol requirement.

Related topics:

ArraySlice.capacity: any legitimate use cases?

Now that we have all the language features we need, I'm working on a proposal to eliminate the ArraySlice type and replace it with just a compatibility typealias ArraySlice<T> = Slice<Array<T>> instead. Hopefully this will both simplify the standard library and help make things clearer for users. To do this, we need to make sure that all the capabilities of ArraySlice come from protocols rather than methods directly on the type. For example, to give Slice<Array> the withUnsafeBufferPointer meth…

Foundation Swift & NSCache

Is a Swifty version of NSCache on the cards for Foundation? NSCache is great for its thread safe behavior and support for automatic purging of items under memory pressure. Unfortunately it doesn't fit so nicely into the type-safe and value type world of Swift. In particular, although it supports lightweight Objective-C generics that are bridged to Swift, it requires that the KeyType and ObjectType be Objective-C classes. This means you can't store Swift Foundation value types like String or Da…