Why do assignment statements return a value?

by

To my understanding, assignment s = “Hello”; should only cause “Hello” to be assigned to s, but the operation shouldn’t return any value.

Your understanding is 100% incorrect. Can you explain why you believe this false thing?

What is the reasoning behind allowing assignment statements to return a value?

First off, assignment statements do not produce a value. Assignment expressions produce a value. An assignment expression is a legal statement; there are only a handful of expressions which are legal statements in C#: awaits of an expression, instance construction, increment, decrement, invocation and assignment expressions may be used where a statement is expected.

There is only one kind of expression in C# which does not produce some sort of value, namely, an invocation of something that is typed as returning void. (Or, equivalently, an await of a task with no associated result value.) Every other kind of expression produces a value or variable or reference or property access or event access, and so on.

Notice that all the expressions which are legal as statements are useful for their side effects. That’s the key insight here, and I think perhaps the cause of your intuition that assignments should be statements and not expressions. Ideally, we’d have exactly one side effect per statement, and no side effects in an expression. It is a bit odd that side-effecting code can be used in an expression context at all.

The reasoning behind allowing this feature is because (1) it is frequently convenient and (2) it is idiomatic in C-like languages.

One might note that the question has been begged: why is this idiomatic in C-like languages?

Dennis Ritchie is no longer available to ask, unfortunately, but my guess is that an assignment almost always leaves behind the value that was just assigned in a register. C is a very “close to the machine” sort of language. It seems plausible and in keeping with the design of C that there be a language feature which basically means “keep on using the value that I just assigned”. It is very easy to write a code generator for this feature; you just keep on using the register that stored the value that was assigned.

More Related Contents:

  1. C# Expressional if statements, possible expansion? [closed]
  2. All possible array initialization syntaxes
  3. What is the C# Using block and why should I use it? [duplicate]
  4. C# – Keyword usage virtual+override vs. new
  5. What are Automatic Properties in C# and what is their purpose?
  6. Why are C# 3.0 object initializer constructor parentheses optional?
  7. What does the ‘=>’ syntax in C# mean?
  8. What does the tilde before a function name mean in C#?
  9. What does “DateTime?” mean in C#?
  10. Difference between wiring events with and without “new”
  11. LINQ, Where() vs FindAll()
  12. Best way to split string into lines
  13. Using Statement with Generics: using ISet = System.Collections.Generic.ISet
  14. A textbox/richtextbox that has syntax highlighting? [C#] [closed]
  15. In c# what does ‘where T : class’ mean?
  16. What does the tilde mean in an expression? [duplicate]
  17. Why is Main method private?
  18. What’s the false operator in C# good for?
  19. Why prefer Properties to public variables? [duplicate]
  20. C# binary literals
  21. C#: Abstract classes need to implement interfaces?
  22. What does the @ prefix do on string literals in C#
  23. C# using numbers in an enum
  24. Is this pattern matching expression equivalent to not null
  25. The name ‘str’ does not exist in the current context
  26. What’s the difference between ‘int?’ and ‘int’ in C#?
  27. Why can’t we define a variable inside a while loop?
  28. Inline property initialisation and trailing comma
  29. Can't implicitly convert type string to int ISSUE [closed]
  30. Writing to a TextBox from another thread? [duplicate]

Leave a Comment