@Dragonrage Funnily enough, Friday is also 11 years old...

Was Rebecca's black the first Skyrim port?!

@Wipqozn naaa, other way around. on Fridays when you go into a tavern the Bards are singing Rebecca Black

let's go

this time brought to you by System.Linq

you really didn't need linq to score a good time today

see I even had time to wake up, go to the bathroom and I still got you beat

tildegit.org/bp/bp-aoc-2022/src/branch/master/3.py#L302

Sets make todays really easy

@badp yeah but .intersect go brrr

Also damn 15 seconds faster

(real)

So many small bugs in my code today. Also, I'm not a huge fan of the C++ standard library set_intersection function.

Fun story I originally used Enumerable.Intersect before I remembered it was also an extension method

So I could just do mystring.Intersect

Ok I switched to Firefox mobile but it hates chat

Well technically I think the first one runs on an IEnumerable<char> but technically string is already an IEnumerable<char>

But I used Take and TakeLast instead of Substring because I could

I could have used the ranges library version, which I think is a little better, but it's also not something I can use at work right now.

That's what's nice about working in .NET, most of it is fair game and stuff I can use for work

Except work uses .NET Framework 4.6 or something and I'm using .NET 7.0

But I mean my code would compile on the older version if it was converted to be a Main style program

Which vs code can happily do automatically

github.com/evanc5/advent-of-code-2022/blob/main/Day03/…

And I'd need to include the namespace and usings instead of implying them

But as long as I'm using super common usings like System.Linq, System.Collections.Generic, etc, I'm good to omit them in this version which is very cool

Well, both std::set_intersection and std::ranges::set_intersection are C++20, which we haven't moved to yet, but the concepts outside of the ranges namespace are more applicable.

The framework isn't holding us back too much for us fortunately

What's holding us back is 10 year old copy pasted code

Though we'd probably see performance gains from newer versions

The plan I think is to fully move everything to C++20 in the new year. There isn't much that needs updating.

Idk what our plan is

My plan is to continue putting refactoring on the plan

And or sneak it in when I can

Since like we're going through a business rules rewrite