Separate NautilusFileInfo implementation
From this discussion:
António Fernandes
For context on the NautilusFileInfo situation:
Apparently some extensions used to exploit the fact that NautilusFileInfo was used to be just an alias for NautilusFile, to use NautilusFile methods, bypassing the extension interface.
When trying to isolate NautilusFileInfo into an interface, in order not to break compatibility with existing extensions, NautliusFile became an implementation of that interface, and a dummy typedef for NautilusFile was included.
This typedef has since been removed because we've broken compatibility anyway during the GTK4 port.
So, I wonder: is it still worth having NautilusFile implement the NautilusFileInfo interface? Maybe we should delegate it to another object class (NautilusFileInfoImpl?).
Not sure if it would be so simple, but maybe NautilusFileInfoImpl could be simply a wrapper object which keeps a ref on a NautilusFile instance.