Turing.jl: Refactoring: move `trace/tarray.jl` and `taskcopy.jl` to `TuringLang/Libtask`
yebai
>All comments
For code organisation purpose, I think we can
- turn
TuringLang:Libtaskinto a Julia package - move move
trace/tarray.jlandtrace/taskcopy.jltoTuringLang/Libtask - clean up code in
trace/tarray.jlandtaskcopy.jl - move related tests from Turing to Libtask
- make Turing depend on Libtask (e.g. install Libtask via
deps/build.jl)
This allows Libtask to be maintained as a separate package. This makes sense since these codes are not Turing specific and can be shared with other packages. Also, Libtask features can be tested in a simpler environment (no more complex Turing interactions), which will be a lot easier to debug and maintain.
@trappmartin @hessammehr @xukai92 what do you think?
yebai
on 4 Sep 2018
👍3
Was this page helpful?
0 / 5 - 0 ratings
Related issues
mateuszbaran
路
5Comments
ClaudMor
路
3Comments
ClaudMor
路
4Comments
Vaibhavdixit02
路
4Comments
trappmartin
路
3Comments
Most helpful comment
For code organisation purpose, I think we can
TuringLang:Libtaskinto a Julia packagetrace/tarray.jlandtrace/taskcopy.jltoTuringLang/Libtasktrace/tarray.jlandtaskcopy.jldeps/build.jl)This allows
Libtaskto be maintained as a separate package. This makes sense since these codes are not Turing specific and can be shared with other packages. Also,Libtaskfeatures can be tested in a simpler environment (no more complex Turing interactions), which will be a lot easier to debug and maintain.@trappmartin @hessammehr @xukai92 what do you think?