Zachary Sunberg

Yes, you should definitely avoid this anti-pattern!! Just create functions without any methods!

(Also, if you do end up having a `ResultsStore` object, you can implement automatic plotting with something like `show(io::IO, mime::MIME, rs::ResultsStore) = show(io, mime, visualize_trajectory(rs))`.

Hi @AlexS12 , hope it isn't rude to jump in like this! I'm an aerospace engineering professor who uses julia - so it seems likely that I will use this...

(I added a couple thoughts related to the discussion above in #70 and #71)

Cool - yes, using methods to get properties is a good pattern! In general, to promote proper encapsulation, I make it a goal to write code so that functions access...

@FlyingWorkshop did you close this because it was resolved? If it can throw an error when it samples a terminal state, we should probably fix that. I think `@gen` should...

Well, "resolved" is an optimistic word, but yes, I think the behavior was changed in a positive way, so I am closing this :)

The reason for the error is that `channel` is not a defined symbol on the other worker processes. `@everywhere` simply executes the code on all the processes, and `channel` does...

https://discourse.julialang.org/t/documentation-about-using-anonymous-and-named-functions-with-pmap/19337

If the tasks are executing asynchronously, there is nothing to keep one task from starting to print while another is in the middle of printing. See #109 for a possible...