Skip to content
This repository has been archived by the owner on Jan 20, 2022. It is now read-only.

Treat Configuration as a mutable object, not immutable #136

Open
johnynek opened this issue Aug 21, 2013 · 1 comment
Open

Treat Configuration as a mutable object, not immutable #136

johnynek opened this issue Aug 21, 2013 · 1 comment

Comments

@johnynek
Copy link
Collaborator

In the scalding code, we are treating the Configuration like an immutable object and passing functions from Configuration => Configuration around, the problem is, Configuration is mutable, and it is not at all clear how to reason about such changes.

I think the better approach is to use the Reader Monad, which is basically combinators on (Configuration) => T and T => ((Configuration) => U)

@johnynek
Copy link
Collaborator Author

Fixing #529 is related here. Using scalding.Execution is probably the way forward.

snoble pushed a commit to snoble/summingbird that referenced this issue Sep 8, 2017
 Adding foldM to Monad and a test
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant