The error tells you it's not a function, but a String. In other words, it's
a property of filemgr. Try calling it without the parentheses :).
On Wed, Feb 1, 2017 at 10:34 AM, Roman Pastushkov via swift-dev <
swift-dev@swift.org> wrote:
> Hello everyone!
>
> I iam trying compile 4 lines prog on li
e erasure seems
>> like
>> > it might confuse things even more.
>>
>> We'll happily take a litte more implementation complexity in exchange
>> for performance gains. 10% is nothing to sneeze at.
>>
>> > On Mon, Sep 5, 2016 at 9:50 PM, Dmitri Gri
exchange
> for performance gains. 10% is nothing to sneeze at.
>
> > On Mon, Sep 5, 2016 at 9:50 PM, Dmitri Gribenko
> wrote:
> >
> >> On Mon, Sep 5, 2016 at 11:13 AM, Chris Eidhof via swift-dev
> >> wrote:
> >> > Hello swift-dev,
> &g
d be a lot more work to write the implementation (and the size would
change a lot). Having two different mechanisms for type erasure seems like
it might confuse things even more.
On Mon, Sep 5, 2016 at 9:50 PM, Dmitri Gribenko wrote:
> On Mon, Sep 5, 2016 at 11:13 AM, Chris Eidhof via swift
Hello swift-dev,
I was wondering why type erasers (e.g. for AnyIterator) are implemented the
way they are. I would implement AnyIterator like this:
final class MyAnyIterator: IteratorProtocol {
var nextImpl: () -> A?
init(iterator: I) where I.Element == A {
var copy = iterator
