drasto

Slovakia/Czech republic

Age: 28

21h
awarded Popular Question
1d
awarded Popular Question
Oct
16
revised How to distribute extensions of Array as a framework?
added 18 characters in body
Oct
16
comment How to distribute extensions of Array as a framework?
@MartinR Edited to clarify that I recognise this as a bug.
Oct
16
revised How to distribute extensions of Array as a framework?
added 4 characters in body
Oct
16
revised How to distribute extensions of Array as a framework?
added 4 characters in body
Oct
16
comment How to distribute extensions of Array as a framework?
@Martin I am not sure that this is an exact duplicate - in the linked question the problem is merely stated as bug while here I know this is a bug and and I am asking if there is a workaround. So the purpose of the question is different but I am not sure whether that is enough to differentiate from linked question. I am also stating more information here then is available in linked question - please see my edit.
Oct
16
revised How to distribute extensions of Array as a framework?
added 337 characters in body
Oct
16
asked How to distribute extensions of Array as a framework?
Oct
16
awarded Notable Question
Oct
13
comment Playground crashes for Recursive Value Type
Hmm, XCode 6.1 is not listed as an update in my App store
Oct
13
comment Playground crashes for Recursive Value Type
@Black Frog XCode 6.0 (6A313). Looks like I really need to update
Oct
13
asked Playground crashes for Recursive Value Type
Oct
10
comment Adding explicit return to closure causes compiler error: A compiler bug?
@dasblinkenlight I would also say so. I wanted to verify it because there are several things about Swift type system that I thought to be bugs but after posting to SO, it was explained to me they were meant to be so or even features.
Oct
10
revised Adding explicit return to closure causes compiler error: A compiler bug?
edited title
Oct
10
revised Adding explicit return to closure causes compiler error: A compiler bug?
edited title
Oct
10
asked Adding explicit return to closure causes compiler error: A compiler bug?
Oct
9
comment Cannot assign class instance to its protocol type?
Thank you for this answer Rob. It answered all my questions (including some I might have asked elsewhere in the future, for example what does Swift team think about this). Unfortunately, I cannot provide any more specific information. I provided artificial example in order to erase all business related information. However , the example given is as near as possible and I state that the product is a library and I can hardly require users to specify type explicitly for many method calls. I have found another way around. Still protocols with open type-aliases to be used as types would be great
Oct
9
comment Cannot assign class instance to its protocol type?
Through personal, it is very good opinion and analyses indeed. Furthermore, if we continue along those lines: Typealiased protocols are replacement for generic protocols (Apple engineers declaring they are better). Your conclusions means that they cannot be used as types (of constants, variables, methods...). In Java or C# that is an equivalent of being able to use only non-genetic interfaces as types. If this analyses are correct this is IMHO serious omission in Swift. I would be very interested in getting opinion of somebody creditable on Swift about the issue.
Oct
9
revised Cannot assign class instance to its protocol type?
added 631 characters in body
1 2 3 4 5