Test your Functional Programming knowledge with a free interactive quiz — 21 questions with answers and explanations. No signup needed to play.
Question 1/5Score 0
What does "partial application" mean, and how does it differ from currying?
Questions in this quiz
What does "partial application" mean, and how does it differ from currying?
What is functional programming (FP), at its core?
What is a "pure function"?
What is a "closure," and how does it relate to functional programming patterns like function factories?
What is "point-free style" (also called "tacit programming") in functional programming?
What does "higher-order function" mean?
What is "declarative" programming (as FP often is), as opposed to "imperative" programming?
What are `map`, `filter`, and `reduce` in the context of functional programming on collections?
What is a "pure" versus "impure" example of a random-number-related function, and why does this matter for referential transparency?
Why do many functional-leaning codebases favor `Result`/`Either`-style return types over throwing exceptions for expected failure cases (like a validation error)?
What is a "side effect" in the functional programming sense?
What is a common trade-off teams weigh when adopting a heavily functional style in a language that isn't functional-first (like JavaScript or Python)?