ChangeTracker does not eliminate unnecessary changes

[natemcmaster]

When add and remove are in the same unit of work, the change tracker still submits a remove StateEntry upon .SaveChanges().

Is this a bug or intentional behavior?

Example:

context.Items.Add(item); // add
item.Count = 12435; // modify
context.Items.Remove(item); // remove

context.SaveChanges(); // requests removal

[ajcvickers]

This is a bug given how the current EF works and how I expect it to work in EF7. That being said, the ability to detect and respond to changes in EF7 is still pretty basic right now so it might be a while before it gets fixed unless it is blocking.