jstedfast / MimeKit

94%

master: 95%

LAST BUILD ON BRANCH unsafe-scancontent

branch: unsafe-scancontent

CHANGE BRANCH

x

Reset

• unsafe-scancontent
• HEAD
• binary-quoted-printable-decoder
• bouncycastle2.0
• core
• crypto-abstractions
• dependabot/nuget/System.Memory-4.5.5
• dependabot/nuget/nunit-4.0.0
• hwaccel-base64
• issue682
• master
• mime-compliance
• mime-compliance2
• mimereader
• mimereader-span
• mimereader-span2
• nullable-api
• nullable-api2
• parser-options-create
• refs/pull/1072/merge
• refs/pull/1162/merge
• refs/pull/1163/merge
• refs/pull/1176/merge
• refs/tags/2.12.0
• refs/tags/3.3.0
• refs/tags/3.4.1
• refs/tags/3.4.3
• rfc2047-perf
• rfc2047-tokens
• smime-revocation-checks
• stream-spans
• unix2dos-indexof
• vnext

Build # 4.9.0.1741

Build Type

push

coveralls.net

Committed by jstedfast

Commit Message

Reintroduce some unsafe pointers in MimeReader for .NET Framework perf

Sadly, Span<T>.IndexOf() is super slow on .NET Framework, so those
optimizations are killing us (~30% performance degradation).

Adding back some unsafe pointers is an attempt to mitigate that, but so far
it has not helped enough.

Will likely need to undo a lot of the Span<T> changes.

Run Details

31154 of 33019 relevant lines covered (94.35%)

0.94 hits per line