Immutable vs mutable object as returned parameter for class method [closed]
It’s difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center. Closed 11 years ago. There is a class method (static method) in […]
What are the drawbacks of immutable types?
I see myself using more and more immutable types when the instances of the class are not expected to be changed. It requires more work (see example below), but makes it easier to use the types in a multithreaded environment.
Is there a concept of a variable with phases of initialization: uninitialized, initializing, immutable?
I was looking at this thread on Stack Overflow and thinking about the functional programming I’ve been learning, and how immutability is so key there, and it occured to me that maybe some language has gotten the idea to have variables start out “null”, then go to a “building” state, and finally become the same as any other immutable when initialization is done.
Is there a concept of a variable with phases of initialization: uninitialized, initializing, immutable?
I was looking at this thread on Stack Overflow and thinking about the functional programming I’ve been learning, and how immutability is so key there, and it occured to me that maybe some language has gotten the idea to have variables start out “null”, then go to a “building” state, and finally become the same as any other immutable when initialization is done.
Is there a concept of a variable with phases of initialization: uninitialized, initializing, immutable?
I was looking at this thread on Stack Overflow and thinking about the functional programming I’ve been learning, and how immutability is so key there, and it occured to me that maybe some language has gotten the idea to have variables start out “null”, then go to a “building” state, and finally become the same as any other immutable when initialization is done.
Is it possible to represent mutation of object-graph efficiently with immutable states?
I am practicing using of immutable object in C++. My personal goal is representing generic object graph (in heap) with sequence of immutable graphs.
Is it possible to represent mutation of object-graph efficiently with immutable states?
I am practicing using of immutable object in C++. My personal goal is representing generic object graph (in heap) with sequence of immutable graphs.
Is it possible to represent mutation of object-graph efficiently with immutable states?
I am practicing using of immutable object in C++. My personal goal is representing generic object graph (in heap) with sequence of immutable graphs.
Is it possible to represent mutation of object-graph efficiently with immutable states?
I am practicing using of immutable object in C++. My personal goal is representing generic object graph (in heap) with sequence of immutable graphs.
When is it NOT good to use actors in akka/erlang?
I’ve been working with akka for 7-8 months now daily.
When I started, I would be working on applications and notice that actors would be used basically anywhere once inside the actor system for communicating between most objects. So I did the same – spin up another actor for x/y/z.