In addition to the reasons posted by Dan: Value types are, by definition those types which store their values in themselves, rather than referring to a value somewhere else. That’s why value types are called “value types” and reference types are called “reference types”. So your question is really “why does a string refer to … Read more
The type of both the expression y and the expression z is int. A reference appearing in an expression won’t keep reference type. Instead, the type of the expression will be the referenced type, with the expression being an lvalue. So in both cases, T is deduced to int, and thus the explicit specialization is … Read more
System.Enum is a reference type, but any specific enum type is a value type. In the same way, System.ValueType is a reference type, but all types inheriting from it (other than System.Enum) are value types. So if you have an enum Foo and you want a nullable property, you need the property type to be … Read more
What you’re looking for are object id’s. For any referenc type in the debugger you can right click and say “Make Object ID”. This will add a # suffix to the value column whenever that instance is displayed in the debugger. You can also add #1, #2, etc … to the watch window to see … Read more
In which case should you use primitive types(int) or reference types (Integer)? As a rule of thumb, I will use a primitive (such as int) unless I have to use a class that wraps a primitive. One of the cases were one must use a wrapper class such as Integer is in the case of … Read more
Yes, they can. Is it a good idea? Well, that depends on the situation. Personally I rarely create my own structs in the first place… I would treat any new user-defined struct with a certain degree of scepticism. I’m not suggesting that it’s always the wrong option, just that it needs more of a clear … Read more
All values in Python are references. What you need to worry about is if a type is mutable. The basic numeric and string types, as well as tuple and frozenset are immutable; names that are bound to an object of one of those types can only be rebound, not mutated. >>> t = 1, 2, … Read more
AnyObject is only for reference types (classes), Any is for both value and reference types. So you should go for [String: Any]. Type Casting for Any and AnyObject Swift provides two special types for working with nonspecific types: Any can represent an instance of any type at all, including function types. AnyObject can represent an … Read more
Re: OP’s Assertion It is universally acknowledged (in C# at least) that when you pass by reference, the method contains a reference to the object being manipulated, whereas when you pass by value, the method copies the value being manipulated … TL;DR There’s more to it than that. Unless you pass variables with the ref … Read more
Is tricky. Will come onto it in a minute. There’s no difference – in both cases, it’s the variable itself which is captured. Nope, no boxing occurs. It’s probably easiest to demonstrate how the capturing works via an example… Here’s some code using a lambda expression which captures a single variable: using System; class Test … Read more