Which value do you want if the collection is empty?
Give me a new question
Copy to clipboard
F# to LINQ table comparison?
How far along is Fabulous?
Is this consistent with what you mean by the functional interaction law?
How does lack of REM sleep for three days affect your ability to remember strings of numbers?
Would aliens understand lambda calculus?
How to make this more idiomatic?
It's easy to criticise office work, but if it's so unpopular, why is it still the mainstream?
Your first Bolero project not compiling?
Is Python better than Go?
What are assumptions that we never question and that determine how programming languages are designed?
Is there a paper one can read to better understand the problem?
What if instead we modeled functionality through time?
Some arbitrary value at an unknown position?
What if instead of trying to model every possible state at rest we modeled the change of state over time?
What about large tuple arities?
Why do I suggest hard limits on line width, cyclomatic complexity, and so on?
Are inheritance and class hierarchies sexy again?
So how does this all translate to our coding practices?
Or, can we learn about software maintenance by looking at how buildings evolve in time?
Should we just give up on purely functional code in the interest of performance?