UnityCsReference VS ILSpy

I've checked their CS reference code on their Github, both here and here, but I want to dive a little deeper - specifically, I want to know what they're actually doing when determining validity of the Matrix4x4.

Yep, but beyond just decompiling it, the c# layer of code is on GitHub: https://github.com/Unity-Technologies/UnityCsReference

https://github.com/Unity-Technologies/UnityCsReference/blob/master/Runtime/Export/Scripting/UnityEngineObject.bindings.cs (after 2019.1)

The code where the method filtering for the Animation Event Inspector is done, is here (line 190). Is it possible to do something like this? That repository explicitly says:

No reason, you can look at the source of encapsulate

There isn't really a straight forward way to do this, even the QualitySettings editor uses Serialised Properties to get at the data. (Line 343 in QualitySettingsEditor)

This is awesome, thank you! I'm most curious about their Runtime

I think if you want to get into graphics programming you do want to work with OpenGL and similar things, because at the very least you need to understand it all (and decide what parts of engines to use and what to ignore when you get to whole games). It's also worth saying that while you can only publicly get the references in Unity you do get source access at the higher subscription tiers you'd use at a game studio.

First, go grab this: https://github.com/icsharpcode/ILSpy. It's a decompiler that will break Rust down. Hope you like C#.

If its a C#/.NET exe you can use ILSpy to get the source code https://github.com/icsharpcode/ILSpy

Well, it might not be exactly what you're asking for, but ILSpy lets you choose what version of C# you wish to decompile an assembly to. This is great for learning how a specific feature used to be coded in C# prior to some new syntax/compiler feature being added.

You will thoroughly enjoy this, then.

I've only used their GUI frontend myself, but ILSpy is also available as a library and command line tool.

As you can see IL code is not exactly human readable, and it's also quite verbose. If you want to have an idea of how your code looks like in IL you can use a decompiler tool such as JustDecompile or ILSpy.

Take a random piece of C# software, run it through ILSpy, and be amazed at the results.