You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 29, 2019. It is now read-only.
Regarding immutability specifically, it first crossed my mind here. In a way, immutability reinforces reproducibility. And the way that drake expects commands that depend on other functions touches on FP a bit. Other parallels have not occurred to me.
I did mention purity in the workshop: Ideally, all commands should be pure or at least idempotent (repeated execution doesn't change the results). That's difficult/impossible to check for drake, it's something that the user needs to keep in mind. But we can help by capturing console output.
Drake does try to counter side effects by wrapping commands in calls to local(). But I agree, other requirements of purity are difficult to check. We could add output to the metadata (alongside warnings and messages) roughly here.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
concept from FP.
The text was updated successfully, but these errors were encountered: