3 ms·
Is this really seen as an abomination in the C# community? My argument for why this is good seems pretty simple: 1) The code that does this isn't that hard to
by aidenn0 17y ago
Is this really seen as an abomination in the C# community?
My argument for why this is good seems pretty simple:
1) The code that does this isn't that hard to understand
2) All code that uses it becomes much more readable
3) The total of all code in #2 is going to be modified more often by several orders of magnitude than the code in #1
- aidenn0 17y agoAfter reading the stack overflow discussion, it's clear there are some reasonable arguments, particularly that it is not good for interoperating with other languages on the CLR. However, it also appears that most people on that discussion would disagree with my point #2 (code using this becomes more readable). That's probably where the interesting things come in to play. For me, I don't care about abuse of syntax, etc. as long as code does what a casual observer would guess it does. Perhaps I'm spoiled by working somewhere where people actually write readable code, and if I worked somewhere else, I would want to forbid any syntax magic whatsoever, but more likely I would just be updating my resume :)