#currying — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #currying, aggregated by home.social.
-
Interesting:
“A Case Against Currying”, Emilia H (https://emi-h.com/articles/a-case-against-currying.html).
Via HN: https://news.ycombinator.com/item?id=47477090
On Lobsters: https://lobste.rs/s/w2x9dq/case_against_currying
#Programming #FunctionalProgramming #FP #Currying #Rants #PLDI #Haskell
-
Interesting:
“A Case Against Currying”, Emilia H (https://emi-h.com/articles/a-case-against-currying.html).
Via HN: https://news.ycombinator.com/item?id=47477090
On Lobsters: https://lobste.rs/s/w2x9dq/case_against_currying
#Programming #FunctionalProgramming #FP #Currying #Rants #PLDI #Haskell
-
Interesting:
“A Case Against Currying”, Emilia H (https://emi-h.com/articles/a-case-against-currying.html).
Via HN: https://news.ycombinator.com/item?id=47477090
On Lobsters: https://lobste.rs/s/w2x9dq/case_against_currying
#Programming #FunctionalProgramming #FP #Currying #Rants #PLDI #Haskell
-
Interesting:
“A Case Against Currying”, Emilia H (https://emi-h.com/articles/a-case-against-currying.html).
Via HN: https://news.ycombinator.com/item?id=47477090
On Lobsters: https://lobste.rs/s/w2x9dq/case_against_currying
#Programming #FunctionalProgramming #FP #Currying #Rants #PLDI #Haskell
-
Interesting:
“A Case Against Currying”, Emilia H (https://emi-h.com/articles/a-case-against-currying.html).
Via HN: https://news.ycombinator.com/item?id=47477090
On Lobsters: https://lobste.rs/s/w2x9dq/case_against_currying
#Programming #FunctionalProgramming #FP #Currying #Rants #PLDI #Haskell
-
Another #CodeGolf puzzle for #JavaScript #WebDev people:
I have n functions that type one argument of the same type and return a boolean.
The current usage is:
function a(b) {
return c(b) && d(b)
}I boiled down a to
a = (b) => [c, d].every(fn => fn(x))I assume, this can be further boiled down via bind/ #PartialApplication/ #Currying
What do you think?
#amCoding #amProgramming #webDevelopment #softwareDevelopment #softwareEngineering
-
Another #CodeGolf puzzle for #JavaScript #WebDev people:
I have n functions that type one argument of the same type and return a boolean.
The current usage is:
function a(b) {
return c(b) && d(b)
}I boiled down a to
a = (b) => [c, d].every(fn => fn(x))I assume, this can be further boiled down via bind/ #PartialApplication/ #Currying
What do you think?
#amCoding #amProgramming #webDevelopment #softwareDevelopment #softwareEngineering
-
Another #CodeGolf puzzle for #JavaScript #WebDev people:
I have n functions that type one argument of the same type and return a boolean.
The current usage is:
function a(b) {
return c(b) && d(b)
}I boiled down a to
a = (b) => [c, d].every(fn => fn(x))I assume, this can be further boiled down via bind/ #PartialApplication/ #Currying
What do you think?
#amCoding #amProgramming #webDevelopment #softwareDevelopment #softwareEngineering
-
Another #CodeGolf puzzle for #JavaScript #WebDev people:
I have n functions that type one argument of the same type and return a boolean.
The current usage is:
function a(b) {
return c(b) && d(b)
}I boiled down a to
a = (b) => [c, d].every(fn => fn(x))I assume, this can be further boiled down via bind/ #PartialApplication/ #Currying
What do you think?
#amCoding #amProgramming #webDevelopment #softwareDevelopment #softwareEngineering
-
Another #CodeGolf puzzle for #JavaScript #WebDev people:
I have n functions that type one argument of the same type and return a boolean.
The current usage is:
function a(b) {
return c(b) && d(b)
}I boiled down a to
a = (b) => [c, d].every(fn => fn(x))I assume, this can be further boiled down via bind/ #PartialApplication/ #Currying
What do you think?
#amCoding #amProgramming #webDevelopment #softwareDevelopment #softwareEngineering
-
Currying in languages with implicit effects seems sketchy—effectful functions returning other functions obscure when effects are interleaved. Users see it as just multiple arguments, not realizing some parameter applications might be expensive. #ProgrammingLanguages #Currying #AutomaticCurrying
-
Currying Explained! 🌟
Named after Haskell Curry, it doesn't involve spices! 🍛
Currying transforms a function into a series of nested functions, each with access to variables via closures. This makes functions more modular and reusable.
#programming #javascript #python #webdev #currying #closures
-
Расширение Функциональных Интерфейсов Java
За годы прошедшие с их появления в Java8 у меня набралась коллекция полезных решений и шаблонов, которые я переносил из проекта в проект, и которые в стандартной версии так и не были осуществлены. Недавно я решил собрать все вместе в небольшом проекте с открытым кодом. В первом релизе проекта расширения охватывают следующие аспекты:
https://habr.com/ru/articles/812451/
#Java #functional_interface #functional_programming #currying #multimethods #exception #exception_handling #extensions #interception #java_21
-
does any #programmingLanguage have something like partial evaluation based on named parameters? so like #currying, but you can add the parameters in any order, and get a function back that that evaluates the still missing parameters?
it seems pretty handy to me…here is an example for how i think this could work in #JS:
-
my talk from #jdconf 2022 about - #functional #reactive with core #java // #exceptions #functionaltraining #jdk #conditions #memoizing #currying #functionalprogramming https://youtu.be/Ly81s7cDcTY
-
my talk from #jdconf 2022 about - #functional #reactive with core #java // #exceptions #functionaltraining #jdk #conditions #memoizing #currying #functionalprogramming https://youtu.be/Ly81s7cDcTY
-
my talk from #jdconf 2022 about - #functional #reactive with core #java // #exceptions #functionaltraining #jdk #conditions #memoizing #currying #functionalprogramming https://youtu.be/Ly81s7cDcTY
-
my talk from #jdconf 2022 about - #functional #reactive with core #java // #exceptions #functionaltraining #jdk #conditions #memoizing #currying #functionalprogramming https://youtu.be/Ly81s7cDcTY
-
my talk from #jdconf 2022 about - #functional #reactive with core #java // #exceptions #functionaltraining #jdk #conditions #memoizing #currying #functionalprogramming https://youtu.be/Ly81s7cDcTY
-
my talk from #jdconf 2022 about - #functional #reactive with core #java // #exceptions #functionaltraining #jdk #conditions #memoizing #currying #functionalprogramming https://youtu.be/Ly81s7cDcTY
-
my talk from #jdconf 2022 about - #functional #reactive with core #java // #exceptions #functionaltraining #jdk #conditions #memoizing #currying #functionalprogramming https://youtu.be/Ly81s7cDcTY
-
my talk from #jdconf 2022 about - #functional #reactive with core #java // #exceptions #functionaltraining #jdk #conditions #memoizing #currying #functionalprogramming https://youtu.be/Ly81s7cDcTY
-
my talk from #jdconf 2022 about - #functional #reactive with core #java // #exceptions #functionaltraining #jdk #conditions #memoizing #currying #functionalprogramming https://youtu.be/Ly81s7cDcTY
-
my talk from #jdconf 2022 about - #functional #reactive with core #java // #exceptions #functionaltraining #jdk #conditions #memoizing #currying #functionalprogramming https://youtu.be/Ly81s7cDcTY
-
Curry - A Raku module for currying functions plus partially applying them #rakulang #currying #FunctionalProgramming #PartialApplication
https://github.com/CIAvash/Curry -
Of course we could choose to avoid #memoization altogether. Avoid #currying. Avoid retaining state. Just pass around argument parameters and recalculate function results every time.
It'll be safer.
And it'll be slower.
So we must come up with something better.
And that can't be achieved with the current version of the #Java #programmingLanguage or the #JVM.
It can't be achieved on current o.s. kernels or any consumer computer chips.
#Immutability is an illusion. -
#Currying in #FunctionalProgramming is a way to temporarily retain a value for later use. The value is retained in a new, scoped function instance.
Wait.
What?
Isn't that quite similar to what the #ObjectOriented #Java #programmingLanguage does when it retains a value in a Class instance, for later use?
Yes.
Yes, it is.
And that makes currying feel like cheating. Which makes #FP languages that allow it, feel like a hack.
So, what else is there? #Memoization? -
The latter should sound familiar to #cleanCode and #functionalPurity advocates: to use a value it must be supplied as an argument / parameter.
And as great as that seems, it flies in the face of 3 decades of #Java history (give or take a few years). Because Java excels at retaining state in Class instances, which feels like the exact opposite of functional purity.
So a Java programmer reading my software will think I'm mad. (Some have said so.)
So, let's talk about #currying.