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 562785
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 13, 20262026-05-13T12:35:29+00:00 2026-05-13T12:35:29+00:00

I know what this code is doing but I’m not sure on the syntax.

  • 0

I know what this code is doing but I’m not sure on the syntax. It doesn’t seem to conform to a “standard” format. Is it mostly LINQ?

return db.Subjects.SingleOrDefault(s => s.ID == ID);

The first part makes sense but it’s the part in the brackets I don’t understand. How can we use s without declaring it? And how are we putting logic into a method call?

  • 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-13T12:35:29+00:00Added an answer on May 13, 2026 at 12:35 pm

    The first part makes sense but it’s the part in the brackets I don’t understand.

    What are you seeing here is a lambda expression. It’s a very special anonymous delegate.

    Is it mostly LINQ?

    Enumerable.SingleOrDefault is a LINQ method, but the lambdas are something independent of LINQ; they just make LINQ incredibly more friendly then it otherwise would be.

    Now, to get specific IEnumerable<Subject>.SingleOrDefault(s => s.ID == ID) returns the unique instance of Subject in the IEnumerable<Subject> that matches the predicate s => s.ID == ID or it returns null if there is no such instance. It throws an exception if there is more than one such instance. At compile-time s => s.ID == ID is translated into a full-blown delegate the eats objects of type Subject and returns a bool that is true if and only if s.ID is equal to ID.

    How can we use s without declaring it?

    The => is the lambda operator. It basically separates the left-hand side of the lambda expression from the right-hand side. The left-hand side are the input variables. It’s equivalent to the parameter list in an explicitly-defined method. That is s in the lambda expression plays the role of s below:

    public bool Predicate(Subject s)
    

    It’s just that you don’t have to declare the type of s as the compiler will infer it.

    The right-hand side the lambda body. It’s equivalent to the body below

    public bool Predicate(Subject s) {
        return s.ID == ID;
    }
    

    What is more, you don’t have to declare the return type; the compiler will infer that to.

    So, in the end it is as if you did the following:

    class MyPredicate {
        public string ID;
        public bool Predicate(Subject s) {
            return s.ID == this.ID;
        }
    }
    

    Then:

    // elements is IEnumerable<Subject>
    // ID is string
    MyPredicate predicate = new MyPredicate();
    predicate.ID = ID;
    elements.SingleOrDefault(predicate.Predicate);
    

    The nice thing is the compiler just automatically spits this out for you when you use a lambda expression.

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

Sidebar

Related Questions

Does anyone know why this code doesn't work. This means, the alert is NOT
Hello everyone don't know why this code works on windows but not on linux
I know this sort of code is not best practice, but nevertheless in certain
I found this on Github, but I do not know what this code is
I know this is so basic, but for some reason it's just not doing
With this code I can download the file but I should know the file
This is not my code. I just arrived at this site and am doing
I know this specific question has been asked before , but I am not
I know this code is correct, I did not write it. I am trying
Okay, I know this question doesn't show research effort, but I've been going through

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.