Skip to content

Immutable.Net 2.0 #21

@mattnischan

Description

@mattnischan

This issue will hold a general list of tasks and/or considerations for the next major Immutable.Net release:

  • Change Immutable and ImmutableBuilder to value types to avoid double allocating with each modify call
  • Create a shared interface between Immutable and ImmutableBuilder
    • Use generic method constraints to avoid boxing?
  • Update to multi-target frameworks
    • Improves dependency graph for library consumers
  • Investigate creation of an API where the object itself can serve as the Immutable, something like:
public class SomeClass : ImmutableClass<SomeClass>
{
    public string SomeString { get; }
}

var someInstance = new SomeClass { SomeString = "someValue" };
var modifiedInstance = someInstance.Modify(x => x.SomeString, "modifiedValue");

Metadata

Metadata

Assignees

Labels

No labels
No labels

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions