Replies: 3 comments
-
Beta Was this translation helpful? Give feedback.
0 replies
-
I think we'd need semantic highlighting to make it look different. That needs some work in the |
Beta Was this translation helpful? Give feedback.
0 replies
-
We have semantic highlighting now. should be easy to differ them now. If they are in the source code. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
At the moment, type families look like a regular type constructor. For example, in the following tooltip in HLS:
It is non-obvious that
AuxiliaryData
is a type family.If there was some visual cue that
AuxiliaryData
is a type family, for example by being rendered in a different colour, then the type would be much easier to understand.Even better would be if the type family was expanded. For example while type above is shown to be
Maybe (AuxiliaryData (ShelleyLedgerEra era))
, the type below could be expanded to say what the type is after type family application, which is toMaybe (Metadata (ShelleyEra StandardCrypto))
Even more better would be if I could see each step of type family application:
Beta Was this translation helpful? Give feedback.
All reactions