• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

jstedfast / MimeKit / 4.12.0.1627 / 1
95%
master: 94%

Build:
Build:
LAST BUILD BRANCH: mime-compliance-violations
DEFAULT BRANCH: master
Ran 04 May 2025 08:01PM UTC
Files 188
Run time 4s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

04 May 2025 07:52PM UTC coverage: 94.815% (-0.03%) from 94.84%
4.12.0.1627.1

Pull #1162

coveralls.net

jstedfast
Refactored MimeReader to use ReadOnlySpan<byte> instead of unsafe byte*

The main advantage of this change is to make the code a bit nicer. The
AsyncMimeReader code, especially, becomes a lot nicer with this change.

The other advantage is that Spans don't interfere with the GC like pinned
memory buffers do, which could theoretically mean that using MimeReader is
less likely to result in memory fragmentation (although not sure on the
real-world consequences of the previous code in practice).

The downside is that ReadOnlySpan<byte>.IndexOf() is *slower* than the
current implementation on .NET Framework and possibly also even .NET Core
where the platform architecture does not have support for SIMD.

That's why this PR is a Work-In-Progress and not yet merged to master.
Pull Request #1162: [WIP] Refactored MimeReader to use ReadOnlySpan<byte> instead of unsafe byte*

32059 of 33812 relevant lines covered (94.82%)

0.95 hits per line

Source Files on job 4.12.0.1627.1
  • Tree
  • List 188
  • Changed 3
  • Source Changed 2
  • Coverage Changed 3
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Build 4
  • b84ebaab on github
  • Prev Job for on mimereader-span (#4.12.0.1626.1)
  • Next Job for on mimereader-span (#4.12.0.1630.1)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc