Apple Developer Documentation Is Missing

Post by eugeniub » Mon, Oct 28, 2019, 3:11 PM UTC

ChrisMarshallNY wrote: post #88

jtchang wrote: post #74

Earlier quoted context omitted.

What is a "cascaded nil-coalescing operator" ?

Think the ternary operator, but worse. In Swift, this is expressed by "??". It means "If the previous test returns nil, then execute what is after the ??". For example, if you have a concrete Int, but the source might be an optional, then you could do something like this: let a = b ?? 0 That means that if b is nil, then set a to 0. Otherwise, set it to whatever value b has. You can chain these, like so: let b: Int? =…

  nameLabel.text = user?.name ?? "Guest"

  if let name = user?.name {
    nameLabel.text = name
  } else {
    nameLabel.text = "Guest"
  }

Post by heisenbit » Mon, Oct 28, 2019, 3:13 PM UTC

nullandvoid wrote: post #56

craydandy wrote: post #42

Earlier quoted context omitted.

And this reminds me of the documentation quality of Symbian around 2005-2007. I would highly recommend the author of the article the check it out, before lamenting Apple's documentation.

I mean it's a discounted OS is it really a comparison? We're talking about one of the biggest platforms in the world here with unlimited money to throw at this problem there is no excuse

Post by eugeniub » Mon, Oct 28, 2019, 3:14 PM UTC

ChrisMarshallNY wrote: post #120

crusso wrote: post #111

Earlier quoted context omitted.

"Think the ternary operator, but worse" Giving the developer succinct ways to prevent program failure from unexpectedly undefined values is a feature.

"Giving the developer succinct ways to prevent program failure from unexpectedly undefined values is a feature." Most languages have had this since the 1960s. It's called the "if" clause. The ternary and nil-coalescing operators are shorthand (sugar) for an if test (or guard, in Swift). Like I said, I actually like them, but I have to be careful, when using them. I really like Swift, but it's quite possible to write…

Post by SkyPuncher » Mon, Oct 28, 2019, 3:15 PM UTC

ChrisMarshallNY wrote: post #70

Some time ago, I was contacted by Apple to apply for a job. My code is insanely well-documented. I like to think that a lot of the inspiration for my code docs comes from Apple's open codebases. Their code is exceptionally well-documented. In any case, as is usual with all employers, these days, they completely ignored the focused, relevant links that I sent them to elements of my extensive portfolio of repos, and, i…

Post by jniedrauer » Mon, Oct 28, 2019, 3:16 PM UTC

sdegutis wrote: post #116

GGfpc wrote: post #104

Earlier quoted context omitted.

To be honest, while documentation is extremely important in the real world, interviews are time-constrained, and it makes no sense to write documentation when you have 45 minutes to implement something like that.

I have personally found that sometimes writing out comments that explain how a confusing function is going to work will help me to understand the ins and outs and flow of the function before writing it, which will in turn help me to actually write the function, especially with algorithmic functions. Those comments might as well be written as long-standing documentation that doesn't change as long as the implementatio…