- /// Implements search over a single .
+ /// Implements search over a single .
///
/// Applications usually need only call the inherited
- ///
- /// or methods. For
+ ///
+ /// or methods. For
/// performance reasons, if your index is unchanging, you
/// should share a single instance across
/// multiple searches instead of creating a new one
/// per-search. If your index has changed and you wish to
/// see the changes reflected in searching, you should
- /// use
+ /// use
/// to obtain a new reader and
/// then create a new from that. Also, for
/// low-latency turnaround it's best to use a near-real-time
- /// reader ().
- /// Once you have a new , it's relatively
+ /// reader ().
+ /// Once you have a new , it's relatively
/// cheap to create a new from it.
///
- /// NOTE:
+ ///
NOTE:
/// instances are completely
/// thread safe, meaning multiple threads can call any of its
/// methods, concurrently. If your application requires
@@ -68,6 +70,14 @@ namespace Lucene.Net.Search
/// synchronize on the instance;
/// use your own (non-Lucene) objects instead.
///
+ ///