Just one more thing - Swift thread - The Something Awful Forums

Register a SA Forums Account here!
JOINING THE SA FORUMS WILL REMOVE THIS BIG AD, THE ANNOYING UNDERLINED ADS, AND STUPID INTERSTITIAL ADS!!!

You can: log in, read the tech support FAQ, or request your lost password. This dumb message (and those ads) will appear on every screen until you register! Get rid of this crap by registering your own SA Forums Account and joining roughly 150,000 Goons, for the one-time price of $9.95! We charge money because it costs us money per month for bills, and since we don't believe in showing ads to our users, we try to make the money back through forum registrations.

The Something Awful Forums > Discussion > Serious Hardware/Software Crap > The Cavern of COBOL > Just one more thing - Swift thread

Kobayashi: Aug 13, 2004; by Nyc_Tattoo

I don't write code for my day job, so I'm much less knowledgeable than most of the people in this thread. I'm trying to get my head around optionals. At a high level, I think it's trying to prevent accidentally using a declared but uninitialized variable from crashing the program. So:

code:

var s1: String   // won't compile because there's no value?
var s2 = "value"  // OK, with String inferred? 
var s3: String?  // OK and essentially means "nil" right now?

Am I on the right track?

# ¿ Jun 3, 2014 18:42

Adbot: ADBOT LOVES YOU

# ¿ May 4, 2024 16:36

Kobayashi: Aug 13, 2004; by Nyc_Tattoo

I think y'all talked about this earlier, but the stuff about collections being copies but arrays being references unless the length changes and then it's a copy seems a little weird to me. Is that normal?

# ¿ Jun 4, 2014 00:19

Kobayashi: Aug 13, 2004; by Nyc_Tattoo

So is Chris Lattner gonna go back to Apple??

# ¿ Jun 22, 2017 06:13

The Something Awful Forums > Discussion > Serious Hardware/Software Crap > The Cavern of COBOL > Just one more thing - Swift thread