Skip to content

Discuss: Break Compatibility? #265

@AdamSpeight2008

Description

@AdamSpeight2008

When would it be beneficial / profitable to break backwards compatibly?

Let's say some future release does that, and then becomes the new base target for compatibility.
What would you add? What would you remove? What would you enhance / improve?

  • No non-generic collections
  • System.Void a first class type.
  • Action<T> is just an alias for Func<T,void>

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions