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
As of 0.14, the Proxy-Zoo should get reduced to just one: Proxy. This means that creating type-class instances for proxied values is no longer possible (as far as I know)
I think it would be nice to have the same functionality for Proxy as well:
-- In Type.ProxyclassKindShowawherekindShow::Proxya->StringinstanceshowkindShow :: (KindShowa) =>Show (Proxya) where
show a = kindShow a
---- In clientdataInt
reflectInt = ...
instanceshow :: KindShowIntwhere
kindShow p = reflectInt p
Does that make sense? Is there an easier way?
The text was updated successfully, but these errors were encountered:
I feel like this would be better done outside of core to see how much usage it gets, and only bring it into core (if not contrib) once the design stabilizes and we agree that it should go here.
Well, let me give a potentially better reason. We're currently discussing whether to even have Show in the first place (see #272). If we suddenly add it here for kinds, it feels like we're repeating history. Having a KindDebug would make more sense to me.
As of 0.14, the Proxy-Zoo should get reduced to just one:
Proxy
. This means that creating type-class instances for proxied values is no longer possible (as far as I know)For example in typelevel-peano (https://github.com/csicar/purescript-typelevel-peano/pull/4/files#diff-7de00383917fea851d52cc5de4f18f87329b6b3f4e2819a8ebcbf9d8c0d85a80R47) I had a
Show
-Instance for typelevel Ints, that would print the value representation:I think it would be nice to have the same functionality for
Proxy
as well:Does that make sense? Is there an easier way?
The text was updated successfully, but these errors were encountered: