@Aaronontheweb Thanks for the compliment.
I strongly agree that unused code should just go away.
That also alleviates the need to discuss the semantics.
@Aaronontheweb @BKAngryKing To be fair in point 2, Where(i => i != item) doesn't have the same behavior as Except([item]). The latter compares using Equals and skips duplicate items from `collection`.
Just finished reading "The Elements of Programming Style" from 1973 by Kernighan & Plauger.
Both insightful and a bit terrifying how few of the 50+ problems in the Fortran and PL/I examples have obsoleted since then.
🚀 Exciting News! Fluent Assertions is partnering with @XceedSoftware to bring our project to new heights! With their resources and support, we’ll continue evolving and enhancing features. Thanks for your support! #FluentAssertions#XceedSoftware#OpenSource#InnovationNuGet
5 years ago I learned about the Type-Dictionary Trick in C#
https://t.co/G6BK1tZdqv
Recently, I finally found a place to apply it to remove a lookup in a ConcurrentDictionary
https://t.co/yOxnoEOKRL
@EgorBo .NET 9 also has this PR with improvements to insertion of vzeroupper for managed->unmanaged transitions.
https://t.co/baIsiib1iV
I had an educating hunt for that issue in:
https://t.co/67BVrTG8yB
@ddoomen With libfuzzer-dotnet (alternative to afl-fuzz) I've found it even easier to fuzz .NET on Windows with SharpFuzz.
I've successfully used it at work to find bugs in various parsers with ~20 line fuzzing harnesses
@ddoomen Anything that makes .net developers fuzz more or improves/eases the experience. We have SharpFuzz, but I'm flabbergasted why fuzzing doesn't seem more widespread in the .net ecosystem.
Since I'm 6 drinks in for 20 bucks, let me tell you all about the story of how the first Microsoft Office 2007 vulnerability was discovered, or how it wasn't.
This was a story I was gonna save for a book but fuck it, I ain't gonna write it anyways.