Closed JasonShin closed 5 years ago
This isn't causing any issues to the existing typeclasses but it will restrict us from scaling out (adding more typeclasses)
We can close this as the PR by @hemangandhi has solved this issue initially. This issue is an ongoing one and has to be part of the coding standard.
The aim of this ticket is to come up with a standard for naming convention used for generics throughout fp-core.
Right now we are facing major issues with this and it eventually leads to incorrect type class signatures.
For example, I came up with below signature for
traverse
G here is used for Applicative and F is for Functor. However, due to the nature of Rust, which requires you to pass-through generics to its children,
F
in Apply is currently used forf
(mappable) and it is already incorrect.The ticket aims to standardise this process and come up with rules around generic name usage.