Lamda is so easy to work with, in my mind when you have the data because
running back to either the api or your database is costly.
This run is used in posting lists of our employees by plant, to an API
service that makes filling out accident reports on-site at our plants
accessible on their phone app.
// sort all data by location
employees.Sort((x, y) => String.Compare(x.Location,
y.Location));
// only active
employees.RemoveAll(x => x.Active == false);
// get rid of all HQ folk
employees.RemoveAll(b => b.Location == "");
On Thu, Jul 30, 2020 at 6:13 PM MB Software Solutions, LLC <
mbsoftwaresoluti...@mbsoftwaresolutions.com> wrote:
> To be honest, I never liked DotNet lambda expressions. This line makes
> my eyes roll.
>
>
> On 7/30/2020 2:17 PM, Stephen Russell wrote:
> > If you are filtering you should consider lamda expressions
> > (x => x.ColumnName != 0).ToArray()
>
> --
> This email has been checked for viruses by Avast antivirus software.
> https://www.avast.com/antivirus
>
>
[excessive quoting removed by server]
_______________________________________________
Post Messages to: ProFox@leafe.com
Subscription Maintenance: https://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: https://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: https://leafe.com/archives
This message:
https://leafe.com/archives/byMID/cajidmykppweqf9cyjmhjk8fwtcsjx6fxxe2n4mrs0-u0oxc...@mail.gmail.com
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
