// Swift3 gets rid of dispatch_once and recommends replacing it with a lazy global.
// That's very straightforward when dispach_once is used to initialize something, but
// isn't an exact match when you want something to execute once, and then become a noop
// in a thread-safe way.

// The following approach seems completely "correct" and I guess actually a bit elegant,
// if by "elegant" you mean "terse and not immediately obvious to the reader, which makes
// you look very clever."

var doOnce: () -> Void = {
    // The side effect that should only happen once
    print("Running once, I hope")

    // A dummy function that's evaluated every time we're accessed
    return {}
}()

doOnce() // Prints
doOnce() // does not print
doOnce() // does not print

// So is this good Swift that readers should simply learn to understand, or is it over-clever Swift
// that has a better answer that is both idempotent and threadsafe?