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
I noticed in some generated docs there are different symbols with same name. For example in purescript-typelevel-prelude@3.0.0/Type.Row, there are two Cons, one being a class re-exported from Prim.Row while the other being a type from Prim.RowList. Both of them have the anchor #t:Cons which creates ambiguity. I suggest we use a different prefix for type classes, so they will be #c:Cons and #t:Cons.
Also all links to Prim are currently dead in that page as it's assuming Prim in the same package.
The text was updated successfully, but these errors were encountered:
I noticed in some generated docs there are different symbols with same name. For example in
purescript-typelevel-prelude@3.0.0/Type.Row
, there are twoCons
, one being a class re-exported fromPrim.Row
while the other being a type fromPrim.RowList
. Both of them have the anchor#t:Cons
which creates ambiguity. I suggest we use a different prefix for type classes, so they will be#c:Cons
and#t:Cons
.Also all links to
Prim
are currently dead in that page as it's assumingPrim
in the same package.The text was updated successfully, but these errors were encountered: