C# 7 looks interesting...
-
Can't wait to have to maintain poorly written code that misuses all these shiny new "features". Fun times ahead of us all! :doh:
“Thinking is the hardest work there is …”
Don't worry, one can already find poorly written aync, lambda and LINQ code today! ;P :-D
A new .NET Serializer All in one Menu-Ribbon Bar Taking over the world since 1371!
-
Can't wait to have to maintain poorly written code that misuses all these shiny new "features". Fun times ahead of us all! :doh:
“Thinking is the hardest work there is …”
I understand your pain! :thumbsup:
GCS d--- s-/++ a- C++++ U+++ P- L- E-- W++ N++ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t++ 5? X R++ tv-- b+ DI+++ D++ G e++>+++ h--- ++>+++ y+++* Weapons extension: ma- k++ F+2 X If you think 'goto' is evil, try writing an Assembly program without JMP. -- TNCaver When I was six, there were no ones and zeroes - only zeroes. And not all of them worked. -- Ravi Bhavnani
-
What's New in C# 7.0 | .NET Blog[^] And Visual Studio "15" Preview 4 | The Visual Studio Blog[^] is much leaner! only 500 MB (instead of 6GB for minimal VS2015 installation) Woop woop! :)
A new .NET Serializer All in one Menu-Ribbon Bar Taking over the world since 1371!
Initial gut call reactions... The current out syntax is klunky, but hiding variable declarations like that is even worse. X| X| X| The out * for "I don't care" is worrying since it will encourage bad behavior by people who're lazy/don't understand what they're doing. Yeah ignoring return variables is a problem now; but I don't think encouraging it is a good idea in the general case. It might make some things like the cluster elephants that are MS Office COM wrappers less painful to use; but the core problem is that the API is a cluster elephant not the language syntax around calling it. :thumbsdown: Type pattern matching, the initial trivial cases are rather pointless IMO (and whoever decided it was OK to combine an if and then on a single line should be force fed his keyboard); but making switches easier to use and more flexible is cool. :thumbsup: The new tuple return feature looks awesome. :thumbsup::thumbsup: Deconstructing it into separate variables when there's no innate reason to keep them bound after the call (eg returning a computation result and any errors/warnings reported by the computation) means I can have my cake and eat it too. :thumbsup::thumbsup::thumbsup: I'm not so sure about general type deconstruction. On the one hand it's just syntactic sugar, on the other my gut reaction is that it could probably be abused horribly somehow. :thumbsup::thumbsdown: Wild cards in tuple deconstruction trigger the same mixed reaction as with wildcard out parameters and deconstructing normal objects. :thumbsup::thumbsdown: Local functions. I missed these many years ago when transitioning from Pascal to C++; now I feel like they're just adding an extra layer of code hiding to no real gain. :thumbsdown: Allowing _'s in numerical literals to improve readability. Looks like a nice minor usability gain with no real downside. :thumbsup: Ref returns are probably a good idea overall; but requiring devs who've never had to think in terms of pointer-fun to deal with stuff like this might cause confusion. :thumbsup: Generalized async types. Sounds like a good idea, but since I haven't done any greenfield dev with an opportunity to experiment with async I don't feel comfortable making a judgement call here. :thumbsup::thumbsdown: More expression bodies takes the fugliest thing in C#6 and smears it over more of the language like a roomba confronted by a fresh turd
-
Don't worry, one can already find poorly written aync, lambda and LINQ code today! ;P :-D
A new .NET Serializer All in one Menu-Ribbon Bar Taking over the world since 1371!
-
What's New in C# 7.0 | .NET Blog[^] And Visual Studio "15" Preview 4 | The Visual Studio Blog[^] is much leaner! only 500 MB (instead of 6GB for minimal VS2015 installation) Woop woop! :)
A new .NET Serializer All in one Menu-Ribbon Bar Taking over the world since 1371!
-
Initial gut call reactions... The current out syntax is klunky, but hiding variable declarations like that is even worse. X| X| X| The out * for "I don't care" is worrying since it will encourage bad behavior by people who're lazy/don't understand what they're doing. Yeah ignoring return variables is a problem now; but I don't think encouraging it is a good idea in the general case. It might make some things like the cluster elephants that are MS Office COM wrappers less painful to use; but the core problem is that the API is a cluster elephant not the language syntax around calling it. :thumbsdown: Type pattern matching, the initial trivial cases are rather pointless IMO (and whoever decided it was OK to combine an if and then on a single line should be force fed his keyboard); but making switches easier to use and more flexible is cool. :thumbsup: The new tuple return feature looks awesome. :thumbsup::thumbsup: Deconstructing it into separate variables when there's no innate reason to keep them bound after the call (eg returning a computation result and any errors/warnings reported by the computation) means I can have my cake and eat it too. :thumbsup::thumbsup::thumbsup: I'm not so sure about general type deconstruction. On the one hand it's just syntactic sugar, on the other my gut reaction is that it could probably be abused horribly somehow. :thumbsup::thumbsdown: Wild cards in tuple deconstruction trigger the same mixed reaction as with wildcard out parameters and deconstructing normal objects. :thumbsup::thumbsdown: Local functions. I missed these many years ago when transitioning from Pascal to C++; now I feel like they're just adding an extra layer of code hiding to no real gain. :thumbsdown: Allowing _'s in numerical literals to improve readability. Looks like a nice minor usability gain with no real downside. :thumbsup: Ref returns are probably a good idea overall; but requiring devs who've never had to think in terms of pointer-fun to deal with stuff like this might cause confusion. :thumbsup: Generalized async types. Sounds like a good idea, but since I haven't done any greenfield dev with an opportunity to experiment with async I don't feel comfortable making a judgement call here. :thumbsup::thumbsdown: More expression bodies takes the fugliest thing in C#6 and smears it over more of the language like a roomba confronted by a fresh turd
I'm not sure I share your disdain for expression bodies. Used with discipline and restraint, I think they can provide a welcom compression of otherwise wasted space (thus improving readability). I site this source as an example of what I consider appropriate usage. Can you point to some examples of egregious usages?
-
I'm not sure I share your disdain for expression bodies. Used with discipline and restraint, I think they can provide a welcom compression of otherwise wasted space (thus improving readability). I site this source as an example of what I consider appropriate usage. Can you point to some examples of egregious usages?
I could start with the first 3 examples in your link (and presumably the rest but I didn't bother to keep reading). They were hideous the first time I saw them and haven't improved with age.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason? Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful? --Zachris Topelius Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies. -- Sarah Hoyt
-
I could start with the first 3 examples in your link (and presumably the rest but I didn't bother to keep reading). They were hideous the first time I saw them and haven't improved with age.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason? Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful? --Zachris Topelius Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies. -- Sarah Hoyt
That's interesting. From my perspective, in those examples I see the "old way" kind of like an old man with a wise brow and pulseless heart, waging all things in the balance of reason, whereas the "new way" seems more like a beautiful maiden, full of fire, with a burning heart and flaming soul. But perhaps that's just the Topelius in me. :)
-
That's interesting. From my perspective, in those examples I see the "old way" kind of like an old man with a wise brow and pulseless heart, waging all things in the balance of reason, whereas the "new way" seems more like a beautiful maiden, full of fire, with a burning heart and flaming soul. But perhaps that's just the Topelius in me. :)
***THWAPP***
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason? Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful? --Zachris Topelius Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies. -- Sarah Hoyt