Not if you structure your data using an appropriate data structure, like a map. After all, this is all structs in dynamic languages are.
> A specific example might be "serialize this json type without having to annotate the fields with how to serialize them".
Aeson does this safely and statically using Haskell's powerful static Generics.
data Foo = Bar Int String deriving (Generic)
instance FromJSON Foo
instance ToJSON Foo
You can get named fields like data Foo = Bar {baz :: Int, qux :: String}But that's what I would do (at least in Java) for this kind of transient transfer object, if left to my own devices.
https://plus.google.com/110981030061712822816/posts/KaSKeg4v...
(I would put myself in the "moderate liberal" camp, even if the languages Steve Yegge lists for that group are not my choice languages)
Sure—but it's in spite of static typing, not because of it. You certainly give up any guarantees of avoiding runtime errors by detecting typing issues at compile time.
https://manosnikolaidis.wordpress.com/2015/08/25/jackson-wit...
That is a property of the library not of the language.
How do you figure? This would require macros or runtime type introspection.
A specific example might be "serialize this json type without having to annotate the fields with how to serialize them".