More informative documentation for RIO module about rio HOT 4 CLOSED

Honestly I am considering whether RIO.Prelude.Reexports should be removed entirely and its contents distributed across other modules. Whether or not something is just reexported from another package isn't really that important for an end-user to know, and having to search multiple places in the documentation for a function definition because you don't know whether it's a reexport is not great.

If we went this route, I think an organisation similar to base would work well - reexports should go in modules like RIO.Text etc already do, and then the most useful ones could then be exported from RIO as well. This would probably be quite a lot of work though.

As for improving haddock, it already expands exported module documentation for modules that are not exported, so for everything other than UnliftIO we could just add them to other-modules.

from rio.

@adituv Agreed, Reexports is a bit weird, seems like it's mostly organization for development of RIO. PR #72 hides export of those modules. It's rather unorganized, though, and results in a funny mishmash of section headers:

from rio.

@snoyberg Do you think that #163 addressed this issue or there is more improvements need to be done to the documentation organization.

from rio.

I think it addressed it, good catch. Closing.

from rio.