Jared Parsons

Full Span<Tee> shirt #span #dotnet

@AbdurRafaySale2 Sorry. This is Redmond only

@jaredpar I am definitely interested in applying. Is it open to me since I am based in Pakistan?

Interested in working in .NET Tooling? My team is hiring for a few roles. This is a great to impact the .NET ecosystem, work with devs all across Microsoft and help drive the .NET platform forward. jobs.careers.microsoft.com/global/en/job/… jobs.careers.microsoft.com/global/en/job/…

Hey #dotnet people! Exciting news! I've launched my YouTube channel: "Dissecting the Code". It's going to be very similar to my blog, where I'll cover .NET internals, performance tips & tricks, and more deep dives. #csharp I've already published the first two videos: ➡️ Episode 0: What You'll Learn Here ➡️ Episode 1: Dissecting Variable Lifetime I hope you'll like it! Please share, subscribe, and let me know what you think! Your support means a lot to me. 🙏 Links to the channel & videos are 👇

@riosgeorge @davidfowl @GarethSeth We want the end result to look as close to possible if you had started with a project in the first place.

@riosgeorge @davidfowl @GarethSeth A top priority of this effort is ensuring we have a smooth, and aesthetic, transition to a real project. Many of our design decisions come down to "okay, but how does that work once the customer transitions to a real project?"

We’re about to take C# to the next level. Look out Python 👀 #dotnet #csharp

@EgorBo @STeplyakov @davidfowl Once you invoke unsafe you are effectively responsible for the safety of your code.

@STeplyakov @davidfowl @jaredpar There are many ways you can expose a pinned pointer out of its fixed scope. You need to either use ref (C# provides some escape analysis for those) or be careful with unsafe code. Making life easier of those who go fully unsafe is not exactly in our priorities 🙂

Hey #dotnet people. Here is the case, I've faced recently (see the image). Do you know a legit case when its ok to save a pinned local into a field? It seems that it should be a warning here. (yeah, I can add a rule to ErrorProneDotNet)

Want to see what went down at Update Conference Prague? Watch the highlights and get ready for next year’s edition! 🎉    More than 40 sessions, top experts, and endless networking opportunities - online or in person.   ✅ Save the date for next year: 13-14 Nov 2025! 🔗 updateconference.net   #UpdateConference #TechEvent #DeveloperLife #Networking #SoftwareDevelopment #Learning #TechConf @itixocz @riganti

@STeplyakov Definitely be interested to see if it caught any issues with us. Or honestly what docs you discovered that better outlined what is / isn't illegal. Getting to the "is this okay or not" has tripped us up a few timse

@jaredpar I've noticed that Roslyn uses a ton of EventSource. Curious if you're interested in such analyzer?

EventSource analysis is coming to ErrorProne Dot Net. Here is a sneak peak of some of the warnings: * Warn on duplicate ids * Warn on unsupported param types * Warn on arg mismatch * Warn on even method not calling WriteEvent

@dotMorten And ignores all the other code. ;)

@jaredpar Movenext moves to the first record but never past the first yield. So dispose triggers the two finally statements only

C# trivia: what does the following print and why?

@dotMorten @timheuer You're welcome x.com/jaredpar/statu…

@dotMorten @timheuer Not to be that guy ... but I was called out.

Another C# pop-quiz: What two lines will this print to the output? Vote in the next tweet

@Capyvara Correct. It's because the `Dispose` method mirrors the try / finally state from the main method. But it _only_ copies the finally blocks, nothing else. So the code between the finally blocks doesn't exist in Dispose

@jaredpar inner finally, outer finally? becuse enumerator only executes anything after the first MoveNext() and I think finally should execute inner to outer.

@CraigSmitham That's a common reaction.

@jaredpar wtf

@dotMorten @timheuer The roslyn team is well aware of this bug because of the week of productivity lost to tracking it down when they introduced said marshalling bug into our own code base :)

@dotMorten @timheuer That produces all kinds of fascinating behavior with the runtimes logic around empty string interning.