And why does it need new requests as opposed to extending `set_class_info`?
Two windows can have the same class but *different* "real class names[^intended]."
To allow this, we have to change the role of `set_class_info` from
- "Fetch or modify the class used by the given window"
to
- "Fetch or modify the class used by the given window *as well as* window-specific information (real-class-name) not specified in the class."
[^intended]: Subclassing USER32 controls happens in per-window fashion, not per-class. The application can reuse the same custom class to subclass BUTTON and STATIC, for example.