Re:Effective Programs: 10 Years of Clojure
by simon_o on Tuesday October 31, 2017 @05:53PM
(#15596923)
I think the Scala version does exactly what you want it to do, but you seem to be confused about something that I can't really pin-point.
> Why do I need a separate Person and Dog class?
You don't. It's an example.
> Can't a dog have a name as well?
It can.
> Why do I need to declare that upfront or ensure that no other part of code can give a Dog a name?
I have trouble understanding the meaning of that sentence.
Re:Effective Programs: 10 Years of Clojure
by Bogdanp on Tuesday October 31, 2017 @05:29PM
(#15596759)
> The Elm version is much better. Except of course I have to upfront at the method signature declare my property requirements -- while that is also a burden, it is a much lesser burden than having ADT/taxonomy of Person, Dog, etc.
Elm (and Purescript) should be able to fully infer the type of that function w/o forcing you to declare which fields you want to use up-front.
Re:Effective Programs: 10 Years of Clojure
by wellpast on Tuesday October 31, 2017 @05:42PM
(#15596850)
How would it infer:
isOld(parseJson(json))
When parseJson may or may not produce an entity with the "age" property?
Re:Effective Programs: 10 Years of Clojure
by Bogdanp on Wednesday November 01, 2017 @06:24AM
(#15599971)
Sorry, I wasn't clear. My point was that you don't have to declare the type of `thing` up front in that example. It would be able to infer that it's a record with an `age` field from the function's definition.
In your example, `parseJson` would have to return a record with an age field, otherwise the compiler would complain. Personally, I think that represents a reasonable tradeoff in ease of use for safety.
The Elm version is much better. Except of course I have to upfront at the method signature declare my property requirements -- while that is also a burden, it is a much lesser burden than having ADT/taxonomy of Person, Dog, etc.