Log

• Bump to nom v7 by Caio 3 years ago
• clippy: Pass new lints by Caio 3 years ago
• Prepare for release 0.6.0 by Caio 3 years ago
• Update dependencies by Caio 3 years ago
• Adapt cantine to tantivy 0.15 by Caio 3 years ago
• Adapt cantine_derive to tantivy 0.15 by Caio 3 years ago
• Adapt tique to tantivy 0.15 💬 by Caio 3 years ago

  Two simple changes:
  
   * SegmentLocalId is now SegmentOrd, so `segment_id` labels
     were also updated to `segment_ord`
  
   * DocAddress is now a struct with named members instead of
     a tuple newtype, so the code is changed to construct
     it like `DocAddress{...}` instead of `DocAddress(...)`
  

• Automated `cargo fmt` run by Caio 4 years ago
• Automated `cargo update` run by Caio 4 years ago
• Prepare for v0.5.0 by Caio 4 years ago
• Update dependencies by Caio 4 years ago
• Bump to quickcheck 1.0 by Caio 4 years ago
• Bump to tantivy 0.14 by Caio 4 years ago
• Move cantine_derive to tantivy 0.14 by Caio 4 years ago
• Small rewording of tique's snip by Caio 4 years ago
• Update tantivy to 0.14 by Caio 4 years ago
• Revert "Temporarily ignore `Dismax::explanation()` test" 💬 by Caio 4 years ago

  This reverts commit 8e231cbf5b1cc537d2d18180c11b493a5563d700.
  

• Formalize that unsafe code is not allowed by Caio 4 years ago
• Move QueryParser docs into the module by Caio 4 years ago
• Drop cargo-readme template by Caio 4 years ago
• Update Cargo.lock 💬 by Caio 4 years ago

  `cargo update`
  

• Move API docs to cantine/ by Caio 4 years ago
• Update Cargo.lock by Caio 4 years ago
• Update cantine dependencies by Caio 4 years ago
• Upgrade nom dependency to 6.+ by Caio 4 years ago
• Use tantivy 0.13 by Caio 4 years ago
• Temporarily ignore `Dismax::explanation()` test 💬 by Caio 4 years ago

  Since a DisMaxQuery is a combination of TermQuery items,
  trying to `explain()` it triggers a bug in tantivy that
  leads to a crash in debug builds.
  
  Upstream issue: tantivy-search/tantivy#915
  

• Ensure we don't seek back when reading postings 💬 by Caio 4 years ago

  This works around the debug-only crash when trying to seek
  to a doc_id that would have appeared before the current
  SegmentPostings cursor.
  
  Since DocSets now come already initialized, `.seek()`ing
  without checking if we're already at the desired position
  is likely a bug (hence the `debug_assert!` biting me, I
  suspect).
  
  On tantivy.git @ 730cceff one can see the subtle bug that
  the assertion can catch. Code that once looked like:
  
      let mut scorer = create_scorer();
      if scorer.seek(doc) != doc {
          ...
      }
  
  Should now look like:
  
      let mut scorer = create_scorer();
      if scorer.doc() > doc || scorer.seek(doc) != doc {
          ...
      }
  

• Use new DocSet/Scorer API 💬 by Caio 4 years ago

  Introduced on tantivy.git @ e25284ba
  
  This changeset is sufficient, however upstream's f71b04acb introduced
  a `debug_assert!(self.doc() <= target)` for `SegmentPostings::seek`
  that looks overzealous to me.
  
  In release mode all tests pass, but given that lot has changed since
  last I looked I'll be double checking the affected functionality
  prior to letting this go wild.
  

• Add links to download the crawl data by Caio 5 years ago