I really don't understand optionals. This code fails with "Call can throw, but
is not marked with try ..." on the program line:t1.mth("abc", s1);
class Test {
private var s1 : String!
func tst() {
let t1 : Test1 = Test1()
t1.mth("abc", s1)
> On Jan 6, 2016, at 1:15 PM, Jens Alfke wrote:
>
> * The requirement of the ‘try’ prefix means that if a function that isn’t
> failable later gets modified to be failable, every call site will now trigger
> a compile error due to the missing ‘try’ keyword. This means the programmer
> who mad
Points well taken.
> On Jan 6, 2016, at 11:02 AM, Jens Alfke wrote:
>
>
>> On Jan 6, 2016, at 9:34 AM, Don Wills via swift-users
>> wrote:
>>
>> Coming from the perspective of business applications market (Java and C#), I
>> see major problems in
[soapbox]
Coming from the perspective of business applications market (Java and C#), I
see major problems in moving to Swift. It's simple too different. The String
class is a disaster. Optionals present a giant spider web of
interconnectedness and syntax idiosyncrasy that does not provide an
Hello Swift-Users,
I am building an automated translator to translate from another programming
language to Swift. It's mostly working, but there is one issue that would be
hard for the translator to deal with - the issue of 'var' vs. 'let'
declarations.
Right now the translator always creates
