I would prefer library functions rather than language constructs, basically if in doubt but it in the library rather than a language construct. Library functions are much easier to discover and document.
> On 4 Jan 2016, at 9:43 PM, John Joyce via swift-evolution > <[email protected]> wrote: > > Hello all > > It feels like Swift has some risk of going the direction of C++ at times. By > that I mean complexity creep. > Increasingly nuanced scoping results in more keywords and constructs. > Useful and good but increasingly complex and steepening learning curve. > > I'd like to kick off discussion of ways to increase discoverability. > > One thought is tools. > In thinking about contextual completions like Xcode's Open Quickly or the > universal field thing in Sublime, it sure seems like some way to invoke a > list of keywords and constructs available-in-the-current-scope would be > helpful. > > Thoughts ? > > _______________________________________________ > swift-evolution mailing list > [email protected] > https://lists.swift.org/mailman/listinfo/swift-evolution _______________________________________________ swift-evolution mailing list [email protected] https://lists.swift.org/mailman/listinfo/swift-evolution
