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 May 27, 2022. It is now read-only.
Right now Montage's Types.hs specifies that a BucketSpec's PoolSpec can be one of two pools (PoolA or PoolB). It should really be that PoolSpec can be any number of pools, especially just one (the most common usage we'd imagine), and not prenamed A and B.
Defining a getPB resolution function for your datatype is also really awkward (and even confusing) because you need to choose PoolA or PoolB (for a non-bump-legacy-user, totally arbitrary semantically), especially when for one pool it doesn't matter.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Right now Montage's Types.hs specifies that a BucketSpec's PoolSpec can be one of two pools (PoolA or PoolB). It should really be that PoolSpec can be any number of pools, especially just one (the most common usage we'd imagine), and not prenamed A and B.
Defining a getPB resolution function for your datatype is also really awkward (and even confusing) because you need to choose PoolA or PoolB (for a non-bump-legacy-user, totally arbitrary semantically), especially when for one pool it doesn't matter.
The text was updated successfully, but these errors were encountered: