RequireQualifiedAccess is another good option I did not think about. Thanks for mentioning it.
I am still evaluating the last option which would eliminate the duplicate tree structures altogether.
The first time I thought of the Effect pattern was in 2018. We were starting a new project and moving away from Elm. I wanted to designate a place for side effects so init/update could remain pure. But I'm sure I was not the first with the idea. And I'm glad to not be the only one finding it useful.
Best wishes!
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Thanks for the great comment!
RequireQualifiedAccessis another good option I did not think about. Thanks for mentioning it.I am still evaluating the last option which would eliminate the duplicate tree structures altogether.
The first time I thought of the Effect pattern was in 2018. We were starting a new project and moving away from Elm. I wanted to designate a place for side effects so init/update could remain pure. But I'm sure I was not the first with the idea. And I'm glad to not be the only one finding it useful.
Best wishes!