Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reuse postprocessing environments in a safer way. #286

Merged
merged 3 commits into from
Apr 1, 2016

Commits on Mar 28, 2016

  1. Reuses postprocessing environments in a safer way.

    The previous implementation of PostProcessPath could potentially
    generate unbounded numbers of environments, as it could generate
    a new robot instance every time we clone into the same environment.
    
    Here, we keep a module-level mapping from environments to
    postprocessing environments and create them on demand, which
    guarantees that each cloned environment will have at most one
    postprocessing environment.
    psigen committed Mar 28, 2016
    Configuration menu
    Copy the full SHA
    4c47ca0 View commit details
    Browse the repository at this point in the history
  2. Better scoping of env usage.

    psigen committed Mar 28, 2016
    Configuration menu
    Copy the full SHA
    00b803d View commit details
    Browse the repository at this point in the history

Commits on Mar 30, 2016

  1. Configuration menu
    Copy the full SHA
    1a3c41a View commit details
    Browse the repository at this point in the history