Jeremy Pritts

Appearance

Low-level Programming ​

cs
ref *(T*)null

Pointers do not scare me. I'm intimately confortable with managing memory lifetimes and ensuring that unsafe code is used safely.

Native Interop ​

Projects like Il2CppInterop and my LibTorchSharp bindings library extensively use unsafe code. P/Invoke makes this necessary and unavoidable.

Span ​

Part of being comfortable with unsafe code is knowing when not to use it. Avoidance is generally a good rule of thumb, and I've refactored several codebases to remove unsafe code and replace it with safe implementations. Span and readonly counterpart made this possible without compromising on performance.

For example, TextureDecoder previously had portions written with unsafe code. This code was copied from other repositories and exhibited correct behavior during my testing. However, rewriting them to be safe code uncovered several out-of-range bugs in the original implementation.