We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Due to the concerns raised in #86, I doubt this idea is desired. Still, I thought I would bring it up as a possible discussion.
The idea is to convert this codebase from using a variant of the StateT monad (i.e. Middleware) into using the indexed capability design pattern (see Exploration - Indexed Capability Design Pattern with Indexed Monad Transformers for context).
StateT
Middleware
In my fork of this repo, I'm exploring what this would ultimately look like if the approach was taken, and what are its pain points would be.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Due to the concerns raised in #86, I doubt this idea is desired. Still, I thought I would bring it up as a possible discussion.
The idea is to convert this codebase from using a variant of the
StateTmonad (i.e.Middleware) into using the indexed capability design pattern (see Exploration - Indexed Capability Design Pattern with Indexed Monad Transformers for context).In my fork of this repo, I'm exploring what this would ultimately look like if the approach was taken, and what are its pain points would be.
The text was updated successfully, but these errors were encountered: