this post was submitted on 24 Sep 2024
122 points (94.2% liked)
Programmer Humor
19564 readers
1364 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
can someone explain what reflections are, plz?
It's the capability of a program to "reflect" upon itself, I.E. to inspect and understand its own code.
As an example, In C# you can write a class...
...and you can create an instance of it, and use it, like this...
Simple enough, nothing we haven't all seen before.
But you can do the same thing with reflection, as such...
Obnoxious and verbose and tossing basically all type safety out the window, but it does enable some pretty crazy interesting things. Like self-discovery and dynamic loading of plugins, or self-configuration of apps. Also often useful when messing with generics. I could dig up some practical use-cases, if you're curious.
You can also optimize this a bit.
You can use Activator.CreateInstance instead of reflecting and invoking the constructor.
You can also call MethodInfo.Invoke, you don't need to create a delegate.
Also worth noting that Source Generators have replaced the need for reflection in many cases.