| 25 |
|
* <tt>descendingEntrySet</tt> return descending views. The |
| 26 |
|
* performance of ascending traversals is likely to be faster than |
| 27 |
|
* descending traversals. Notice that it is possible to perform |
| 28 |
< |
* subrange traversals in either direction using <tt>SubMap</tt>. |
| 28 |
> |
* subrange traversals in either direction using <tt>navigableSubMap</tt>. |
| 29 |
> |
* Methods <tt>navigableSubMap</tt>, <tt>navigableHeadMap</tt>, and |
| 30 |
> |
* <tt>navigableTailMap</tt> differ from the similarly named |
| 31 |
> |
* <tt>SortedMap</tt> methods only in that the returned maps |
| 32 |
> |
* are guaranteed to obey the <tt>NavigableMap</tt> interface. |
| 33 |
|
* |
| 34 |
|
* <p>This interface additionally defines methods <tt>firstEntry</tt>, |
| 35 |
|
* <tt>pollFirstEntry</tt>, <tt>lastEntry</tt>, and |
| 244 |
|
* <tt>fromKey</tt> and <tt>toKey</tt> are equal, the returned |
| 245 |
|
* navigable map is empty.) The returned navigable map is backed |
| 246 |
|
* by this map, so changes in the returned navigable map are |
| 247 |
< |
* reflected in this map, and vice-versa. Note: This |
| 244 |
< |
* method differs from <tt>SortedMap.subMap</tt> only |
| 245 |
< |
* in that the returned map is guaranteed to support the |
| 246 |
< |
* <tt>NavigableMap</tt> interface. |
| 247 |
> |
* reflected in this map, and vice-versa. |
| 248 |
|
* |
| 249 |
|
* @param fromKey low endpoint (inclusive) of the subMap. |
| 250 |
|
* @param toKey high endpoint (exclusive) of the subMap. |
