User Tools

Site Tools


principles:rule_of_explicitness

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Next revisionBoth sides next revision
principles:rule_of_explicitness [2021-09-02 12:38] – old revision restored (2021-05-19 11:23) 65.21.179.175principles:rule_of_explicitness [2021-09-02 20:12] – old revision restored (2021-05-11 22:22) 65.21.179.175
Line 23: Line 23:
 ===== Rationale ===== ===== Rationale =====
  
-If something is realized explicitly, it is easier to understand. Implicit solutions require the developer to have a deeper understanding of the module as it is necessary to "read between the lines". Implicit solutions also tend to be more complex. So explicit solutions are assumed to be less error-prone and easier to maintain. 
  
 ===== Strategies ===== ===== Strategies =====
Line 103: Line 102:
 ===== Description Status ===== ===== Description Status =====
 /* Choose one of the following and comment out the rest: */ /* Choose one of the following and comment out the rest: */
-/*[[wiki:Stub]]*/ +[[wiki:Stub]] 
-[[wiki:Incomplete]]+/*[[wiki:Incomplete]]*/
 /*[[wiki:Complete]]*/ /*[[wiki:Complete]]*/
  
Line 113: Line 112:
   * Tim Peters: //[[http://www.python.org/dev/peps/pep-0020/|The Zen of Python]]//   * Tim Peters: //[[http://www.python.org/dev/peps/pep-0020/|The Zen of Python]]//
  
-===== Discussion ===== 
- 
-Discuss this wiki article and the principle on the corresponding [[talk:principles:Rule of Explicitness|talk page]]. 
principles/rule_of_explicitness.txt · Last modified: 2021-10-18 22:06 by christian