Carl A. B. Pearson

Roughly correct re my use case of interest, but the library I'm building also provides flexibility to hash somewhat arbitrary (though always small) objects. The users should be providing a...

> "Objects" are still SEXP-representable. If you can call `digest::digest())` on it we should be able to do it at the C level too, with fewer checks and faster. Or...

> This can be done as part of the manuscript that [@jamesmbaazam](https://github.com/jamesmbaazam) is writing with [@pearsonca](https://github.com/pearsonca) as a nice open source contribution? I am imagining basically pulling out a single...

welp, i'm happy to bang out a draft PR that incorporates the distinct pipeline elements by copy-pasting those into the shell of some other current vignette here. can't commit to...

1.(2), yep - though pop isn't an intervention? 2. yep, convert to an intervention. 3. not sure what's being asked here. Something that I'm thinking about here that's maybe related:...

I'm a bit wary of the test changes in #98 relaxing the shouldn't-ever-go-extinct case. Perhaps there need to be other parameter tweaks to ensure non-extinction dynamics (more initial cases?), but...

> It's stochastic so won't any solution here be similarly arbitrary? We can never fully ensure non-extinction dynamics (except by tweaking the seed, but I don't see how that's necessarily...

Sounds reasonable - codify in CONTRIBUTING.md or some such?

Would want to double check the argument prefix collision part, but I think the rest has been addressed. Could definitely spin off whatever might remain into a more targeted issue.

I've lost track of the model diagram here, but I thought transmission from isolation was definitional precluded (currently - I agree it might be interesting to model e.g. household transmission)?