-
Notifications
You must be signed in to change notification settings - Fork 108
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
String names in codecs #15
Comments
Do you mean changing: val result: (String, CursorHistory) \/ A to val result: CursorHistory \/ A ? If so I think I've got this done, surprising how much I've had to change. |
Absolutely agree with EncodeJson - been trying to.convince you of that for ages. Absolutely disagree with DecodeResult loses information if there is no replacement mechanism. |
I'm much less convinced of the change to DecodeResult than I am of the EncodeJson/DecodeJson name. |
Modelling this in haskell makes it pretty obviously a mistake in both cases. The better (replacement) behaviour is to change the type of the value kept in history, which may include "the decoder name." Of course, this should all be polymorphic to emphasise that point. Haskell is nearly complete. Stand-by. |
On Dec 31, 2012 12:04 PM, "tonymorris" [email protected] wrote:
Nope. Loses information. The codec name is not the important thing. There
|
You're right. I think the String part sticks out as fugly especially because it is a String. Pairing any other value looks fine. The encoder is where the more obvious improvements were made by removal of the String. Perhaps only that should be removed and leave the decoder as is as a separate issue (i.e. String iz suckz). |
…and added a couple more library functions to EncodeJson
The String name in EncodeJson and DecodeResult are an extremely bad idea. They need to disappear.
The text was updated successfully, but these errors were encountered: