DiffUtil.DiffResult

public static final int NO_POSITION = -1

Signifies an item not present in the list.

public int convertNewPositionToOld(@IntRange(from = 0) int newListPosition)

Given a position in the new list, returns the position in the old list, or NO_POSITION if it was removed.

public int convertOldPositionToNew(@IntRange(from = 0) int oldListPosition)

Given a position in the old list, returns the position in the new list, or NO_POSITION if it was removed.

public void dispatchUpdatesTo(@NonNull RecyclerView.Adapter adapter)

Dispatches the update events to the given adapter.

For example, if you have an Adapter that is backed by a List, you can swap the list with the new one then call this method to dispatch all updates to the RecyclerView.

    List oldList = mAdapter.getData();
    DiffResult result = DiffUtil.calculateDiff(new MyCallback(oldList, newList));
    mAdapter.setData(newList);
    result.dispatchUpdatesTo(mAdapter);

Note that the RecyclerView requires you to dispatch adapter updates immediately when you change the data (you cannot defer notify* calls). The usage above adheres to this rule because updates are sent to the adapter right after the backing data is changed, before RecyclerView tries to read it.

On the other hand, if you have another AdapterDataObserver that tries to process events synchronously, this may confuse that observer because the list is instantly moved to its final state while the adapter updates are dispatched later on, one by one. If you have such an AdapterDataObserver, you can use dispatchUpdatesTo to handle each modification manually.

public void dispatchUpdatesTo(@NonNull ListUpdateCallback updateCallback)

Dispatches update operations to the given Callback.

These updates are atomic such that the first update call affects every update call that comes after it (the same as RecyclerView).