palimondo
April 15, 2018, 11:06am
16
I think I have worked my way towards a simpler suggestion for curbing the bikeshedding in
Looking for the root cause of grammatical obsession that burdens our naming discussions, exploring the commit history proved quite illuminating. To support the fundamental value of ”Clarity at the point of use”, the Swift API Guidelines section on Naming elaborates how to achieve it using a set of principles presented in three groups.
There is a marked difference in tone between them, with second section consisting mainly of prescriptive rules about what grammatical forms to use when naming var…
How about a minimal tweak to the guidelines like this:
palimondo:gh-pages ← palimondo:end-the-bikeshed
opened 10:11AM - 15 Apr 18 UTC
The emphasis on “**gramatical** English phrases” creates a red herring that side… tracks Swift Evolution process into prolonged bikeshedding of names. The main leverage for achieving clarity at the use site, when designing new API, is provided by [Fluent Interface](https://martinfowler.com/bliki/FluentInterface.html) programming style and not the overzealous application of English grammar.
This change basically reverts the https://github.com/apple/swift-internals/commit/dc661fd60503452a4b82c6f5f7393eb8679aca39 by moving the principle into previous section and removes the word ‘grammatical’.
@forum_admins , could you please review if my 4 solo posts (tagged culture ) are deemed excessive and if so, merge them into this thread in order of creation?
