5 Best Practices For F# Development
- 1. 5 Best practices for F# Development
- 3. HOW THIs will work1. Define the Best Practice2. Explain Why It’s Good3. Provide Concrete Examples
- 4. PROGRAMMING IN THE SMALLPrefer small functions with only one primary responsibility.
- 5. Why is it good?1. Helps enable function composition2. Follows the Single Responsibility Principle (SRP)
- 6. Examples1. FSharpCouch2. IoC Container
- 7. Function compositionPrefer function composition over argument passing.
- 8. Why is it good?1. Allows for function chaining2. Makes the code terse yet readable
- 9. Examples1. Asynchronous Workflows2. WebSharper 2010
- 10. Tail Recursive functionsMake sure your recursive functions are tail recursive.
- 11. Why is it good?1. Without it, there’s a risk for a stack overflow2. Tail Call Optimization (TCO)
- 12. Examples1. Tail Recursive vs. Non-Tail Recursive2. Polyphony (Join the Node Cluster)
- 13. Verifying tail recursionNot tail recursive
- 14. Verifying tail recursiontail recursive
- 15. Active patternsPrefer active patterns over multiple ‘when guards’ during pattern matching.
- 16. Why is it good?1. Makes code more readable2. Supports Don’t Repeat Yourself (DRY)
- 17. Type of active patternsSingle-CaseExample: let (|UpperCase|) (x:string) =…Multi-CaseExample: let (|Odd|Even|) x =…PartialExample: let (|DivisibleByTwo|_|) input =…ParameterizedExample: let (|MultipleOf|_|) x input = …- http://blogs.msdn.com/b/chrsmith/
- 18. Examples1. Example of Active Patterns (XML parse)2. Node Join in Polyphony (DHT)
- 19. Pattern MatchingPrefer pattern matching to if/else syntax.
- 20. Why is it good?1. Makes your code easier to extend2. Helps get you out of the procedural mindset
- 21. Examples1. MVC Template (Account Controller)