[Feature Req.] Better user-facing API #29
Labels
API Breaking
A change that breaks backwards compatibility
type: feature: code
New ability in the code (user-side)
type: refactor
Code refactoring / restyling for internal benefit
Milestone
I think the user-facing API at the moment is a little unintuitive. Various methods are exposed, such as
setup
, which the user should never have to call (they are called by the MCMC routine itself).I think we should think hard about a better API.
The text was updated successfully, but these errors were encountered: