Comments (6)
I think I feel the same way, especially with comp. Sometimes they're better, sometimes I think they make code harder to read; I wouldn't make a blanket recommendation for them.
from clojure-style-guide.
Rich has said multiple times he thinks anonymous functions are more idiomatic than those others and I think he even said that he might omit those others if he did Clojure over?
So, yeah, I agree these recommendations in the guide are probably overreach or at least very subjective.
from clojure-style-guide.
I think I feel the same way, especially with comp. Sometimes they're better, sometimes I think they make code harder to read; I wouldn't make a blanket recommendation for them.
My line of thought exactly.
from clojure-style-guide.
I've updated the guidelines as discussed above. See https://github.com/bbatsov/clojure-style-guide#anonymous-functions-vs-complement-comp-and-partial
from clojure-style-guide.
Rich has said multiple times he thinks anonymous functions are more idiomatic than those others and I think he even said that he might omit those others if he did Clojure over?
I guess that's a good argument to flip the guidelines then.
from clojure-style-guide.
There's a bit more on the topic here - https://ask.clojure.org/index.php/8373/when-should-prefer-comp-and-partial-to-anonymous-functions
from clojure-style-guide.
Related Issues (20)
- Use keys of different length in let & map alignment example HOT 1
- Consider adding :no-doc under common metadata HOT 2
- Consider talking about defprotocol and deftype a bit more? HOT 2
- Multimethod Dispatch Val Placement advice impractical with docstring or attr-map HOT 2
- Clarify `if` indentation HOT 3
- Improve title HOT 2
- x, y - numbers -- only if x and y appear together? HOT 1
- Add note about preferring `(if-not (= ...))` over `(if (not= ...))` and `(when-not (= ...))` over `(when (not= ...))` HOT 8
- Add section about Yoda conditions HOT 1
- No guidance on function arguments naming? HOT 1
- Add note about putting then and else forms on separate lines in `if` HOT 3
- cond-> and cond->> :always test expression HOT 6
- Idiomatic namespace alias for clojure.spec.alpha should be `s` instead of `spec` HOT 5
- Clarify `ns` form rules HOT 3
- The link to "The Joy of Clojure" is dead. HOT 4
- The link to "Clojure Programming" is dead HOT 1
- Italian translation HOT 1
- Threading macro alignment of first argument on it's own line HOT 2
- Test naming inconsist with function naming. HOT 4
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from clojure-style-guide.