I just found that `reload()` sometimes doesn't work at all. I `reloaded` a
module that I modified. But I still see the same results as before the
package was modified. Btw, this module is a local module, not a package
installed via `Pkg.add()`. What might be a possible cause?
Another question: I'm working on a module (let me call it C) which uses two
other modules, say, A and B. C uses A and B, so the beginning of C looks
like
using A
using B
But B uses A too. So B starts as
using A
Can this kind of multiple `using` cause any issues? Does it, at least, add
more work to the compilation stage?
On Saturday, July 2, 2016 at 3:18:04 AM UTC+1, Cedric St-Jean wrote:
>
> I don't have a great solution to this, but this is what I do...
>
> 1. I think that `reload("PackageName")` should work without workspace().
> See http://docs.julialang.org/en/release-0.4/manual/workflow-tips/
> 2. I use `Autoreload.jl`. It's unfortunately not actively maintained, but
> it works well enough for now if you don't have parametric types in the
> autoreloaded modules
> 3. Reloading works better if you `include` files into one big module
> instead of having multiple modules.
>
> I know, this sucks, but IIUC it's on the roadmap to improve this before 1.0
>
> Cédric
>
> On Friday, July 1, 2016 at 9:37:32 AM UTC-4, chobb...@gmail.com wrote:
>>
>> Bump up..
>>
>
