This is a silly mistake I always make with #dotnet and static members. Static members are initialized in the order they are declared, which means, in this case, Iโ€™ll get two entries of nulls in my collection because theyโ€™re not initialized yet.

#JetBrainsRider warns me that I have an issue.

@khalidabuhakmeh

"initialized in the order they are declared"

although it is nice that is specified, it seems very fragile to depend on that

at least in C#, maybe good for F# as that is all top-down evaluated I think

@pero @khalidabuhakmeh F# is evaluated top-down unless a type, module, or namespace is marked recursive.
@khalidabuhakmeh you know whatโ€™s coming ๐Ÿ˜€:
You could use this other dotnet language that prevents such nonsense ๐Ÿ˜…

@khalidabuhakmeh holy crap. That's why I was having an issue with a static method a while back I bet... what an idiot. My solution was to just make the static method not static and force an object...

I'm notorious to some in my habit of declaring variables when I need one and moving them to the top later (if I remember which I'm notorious because I don't remember a lot)