3 ms·
I talked about c#'s lambda syntax, which Java later borrowed, below. For the other points: I have seen a little of the interface vs function conversions in mod
by SideburnsOfDoom 11y ago
I talked about c#'s lambda syntax, which Java later borrowed, below. For the other points:
I have seen a little of the interface vs function conversions in modern Java, and it seems a decent enough small convenient feature in the context of Java, but it doesn't feel like a big win that I would cry out for in C# code.
Defaulting to not-null and immutable values is a trend in several recent languages, e.g. from Swift and Rust to F#. This IMHO looks like a good step forward and I welcome it, however it's hard to see how this would be comprehensively added into existing languages like Java or C# with an existing legacy of not working that way. Opting into Not-null in c# has been talked about many times (1) in various forms, even implemented using attributes (similar enough to type annotations). (2)
1) http://twistedoakstudios.com/blog/Post330_non-nullable-types-vs-c-fixing-the-billion-dollar-mistake http://twistedoakstudios.com/blog/Post330_non-nullable-types...
2) http://stackoverflow.com/questions/792531/c-how-to-implement-and-use-a-notnull-and-canbenull-attribute http://stackoverflow.com/questions/792531/c-how-to-implement...