Decide what to do with the interleave() function

[henriquesposito]

Since resequence() was moved to messydates, interleave is now is a function in qCreate and a helper function in messydates (since it is called by resequence() and because messydates is on CRAN it cannot/should not have GitHub dependencies).

A couple of options:

1. Once a new version of messydates is live we could, for example, export interleave() there and either call the function in qCreate from messydates or a make it wrapper function in qCreate for it.

2. We can better incorporate the interleave code into resequence() within messydates and keep interleave() as an exported function from qCreate.

[jhollway]

Hmm, I wonder whether it might be more efficient to have it be in qData (when it is on CRAN) and then used by both?

[jhollway]

Would it perhaps make sense to have interleave be an exported messydates function?

[henriquesposito]

This is a good idea! I will get into that right away.