Open turion opened 1 year ago
@reubenharry what do you think about that?
That's fine with me. Especially now that rhine-bayes exists, the streaming stuff is not so important. I think the docs may mention the tui, which uses mcmcP, but other than that, I think splitting it out should be straightforward.
How about the following proposed directory structure:
monad-bayes
: Main library, containing src
, test
, benchmark
, models
, monad-bayes.cabal
monad-bayes-pipes
: All parts that also have pipes as a dependencyFine with me, although if it requires more than a little work, it seems to me like not a good use of time, since monad-bayes is unlikely to have many users beyond us. Note btw that the notebooks have a wide variety of dependencies, and those are separated, using nix, from the main dependencies of monad-bayes. Perhaps the pipes examples could just be put in notebooks too?
Right now, when one wants to install
monad-bayes
, it pulls inpipes
as a dependency, and with that many other dependencies completely unrelated tomonad-bayes
. I'd recommend splitting out the parts that usepipes
(I think it's just a streaming example?) into a separate librarymonad-bayes-pipes
in the same repository. That way, the dependency tree ofmonad-bayes
is much more lightweight, which makes it easier for other to use it.