In computer programming, a mirror is a reflection mechanism that is completely decoupled from the object whose structure is being introspected. This is as opposed to traditional reflection, for example in Java, where one introspects an object using methods from the object itself (e.g. java.lang.Object::getClass() to get a java.lang.Class<?>).
Mirrors adhere to the qualities of encapsulation, stratification and ontological correspondence.1
Benefits
Decoupling the reflection mechanism from the objects themselves allows for a few benefits:
- The object's interface is not polluted, so there is no danger of breaking reflection by overriding a reflective method.
- There can be different mirror systems.
- The mirror system can be removed entirely (potentially allowing for optimizations).
- A mirror system can operate on remote code, since it is not coupled with a particular machine.
Languages that use mirrors
- C++, via the
^^operator and the returned typestd::meta::info.2 - Dart, via its
reflect()function. - Inko,3 via its
std::mirrormodule. - Rubinius (Ruby implementation), via its
Rubinius::Mirror.reflect()method.4 - Scala5
- Swift, via its
reflect()function.
References
References
- Gilad Bracha and David Ungar, "Meta-level Facilities of Object-Oriented Programming languages"
- cppreference.com. "std::meta::info". cppreference.com. Retrieved 19 May 2026.
- "Frequently Asked Questions".
- "Rubinius/Mirror.rb at master · rubinius/Rubinius".
- "Environment, Universes, and Mirrors".