Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 710879
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 14, 20262026-05-14T04:40:20+00:00 2026-05-14T04:40:20+00:00

Why only one overload throws this exception? Little update: I understand that there was

  • 0

Why only one overload throws this exception?

Little update: I understand that there was a design decision made by framework developers. The question is really why that decision has been made, is there a related design pattern or whatever? Because if I was designing that I’d return default(TSource). What is wrong with such approach?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-14T04:40:20+00:00Added an answer on May 14, 2026 at 4:40 am

    The one overload that throws the exception takes arguments of type IEnumerable<TSource> (this) and Func<TSource, TSource, TSource>. It starts with the first value and accumulates from there. Without a first value (if source is empty), there’s no way for the function to know what to return.

    The other two overloads accept an argument of type TAccumulate to act as the seed. Even if source is empty in this case, the function can simply return the seed value.


    Update: You ask why the decision was made not to simply use default(T) in the case of an empty sequence. The answer doesn’t boil down to any specific pattern or known idiom, but rather simply to what is (in my opinion) the sensible choice in terms of API design. The point of Aggregate is to make it easy for developers to implement calculations for their own domain-specific problems, without making assumptions about the semantics of those calculations.

    To use default(T) in the case of an empty sequence would be making not one but two pretty big assumptions:

    • that this calculation should produce a meaningful result in the case of an empty sequence; and
    • that this result should be default(T)

    As a trivial counter-example to the first assumption, let’s say I use Aggregate to compute the mode of a sequence of integers. This should give me the value occurring most frequently in the sequence, so a result of zero would simply be false (since the value 0 never occurs in an empty sequence).

    As a counter-example to the second, suppose I take the product of reciprocals of a sequence of positive integers:

    Aggregate [1, 2, 3, ...] -> 1 * 1/2 * 1/3 * ...
    

    In this case the result would actually approach zero as the sequence gets larger, so a default value of zero would, again, be completely misleading.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.