Nick Strupat

Ah yes, I missed that. Should the 16 be 8? In both places (https://github.com/odinmillion/Phf.Net/pull/1/files#diff-c0abc29d441dd7573197a5233567ba9bR207)

> It is covered. `default(Result)` represents `default(int)`. If `default(T)` is a valid state for T (such as with `int` and most other value types), then it's fine. However, if `T`...

Sorry, to clarify, I meant that `default(Result)` (when `nullable` is enabled) will act as if the value was set to a valid, non-null, string.

Yea I think in general there should never be a `0`/`null` `ref`. That said, there are some framework methods that return `null` `ref`s, such as [CollectionsMarshal.GetValueRefOrNullRef](https://learn.microsoft.com/en-us/dotnet/api/system.runtime.interopservices.collectionsmarshal.getvaluerefornullref?view=net-9.0#system-runtime-interopservices-collectionsmarshal-getvaluerefornullref-3(system-collections-generic-dictionary((-0-1))-alternatelookup((-2))-2)) and [Unsafe.NullRef](https://learn.microsoft.com/en-us/dotnet/api/system.runtime.compilerservices.unsafe.nullref?view=net-9.0). As far...

A hard-coded list of framework methods that might return/assign `null` `ref`s would "work", but it wouldn't be amazing haha. Also, hey, I grew up in London ❤

How does .NET (edge_nativeclr.node) do this?

Any luck with this?

I believe I'm running into this issue as well. .NET SDK 9.0.301 macOS 15.5