IWorld <> WorldContext interfaces

[holic]

• Should IWorld include WorldContext methods in its interface? (e.g. via an IWorldContext)
• Can we overload IWorld's usage of WorldContext methods to return _world() as IWorld rather than address?

[alvrs]

Should IWorld include WorldContext methods in its interface? (e.g. via an IWorldContext)

WorldContext is the base contract for things that are called by the World (mostly System), can you elaborate what the use case would be to add it to the World contract itself?

Can we overload IWorld's usage of WorldContext methods to return _world() as IWorld rather than address?

The reason it returns address atm is that consumers likely want to cast it to their local World (which includes function selectors for all of their registered systems), so if we returned it as IWorld they'd first have to cast it back to address