Jeffrey Stedfast

I refactored ImapStream to have fully sync versions (i.e. no calling an Async function with doAsync = false).

based on my findings on a (admittedly) tiny mailbox of 96 messages, byte[] allocations dropped by 2/3rds, MemoryStream allocations dropped by 100% (which was the main source of byte[] allocs),...

FWIW, I sub'd to the Linux Kernel Mailing List and the GCC mailing list which should be high-traffic enough that I'll build up a significant Inbox over the next few...

Awesome, thanks for the pointer!

In my testing, I went from 34.5 MB a week ago to 28.5 MB total allocations now (and I'm up 7,000 messages from a week ago, too - currently at...

I don't think I can go much farther with this unless I have 2 complete code paths - 1 for sync and 1 for async. The FetchSummaryItemsAsync method is at...

Okay, so here's what I think will be my plan: I'll make a release soon with the current fixes and long-term I'll start moving toward having a fully-sync implementation as...

I'm working on unwinding some of the other lower-level I/O methods to avoid async/await overhead. Unfortunately, I lost my access to my JetBrains license because I foolishly updated my email...

JetBrains fixed my license issue so now I can use dotMemory again :) I'm curious as to how much difference my last few commits made (forgot to tag most of...

I'll focus on that next.