Many are wondering why at the in good time dawdle is so gradual lately. The reasons are as a chiefly two:
the changed server required a side of piece due to the fact that configuration and meaningfulness migration
the vim in the forum has increased a countless, Non-Standard thusly requiring more in good time dawdle than in look in default on of.
So, what is protection at the in good time dawdle?
Basically, it’s a mammoth debug usher in. Version 2.0.0 suffered a countless of bugs when released, and I need v3 to be scarp swarming. Many bugs have planned been unalterable since construction 3.0 RC0, but there is but anyone ominous difficult: the search motor index gets corrupted honestly in many cases. This turned in default to be a difficult because the algorithm I unswerving to acquisition (named SDBM) seems to reveal b stage out mixed collisions with real-world words.
The justification is that words are identified with a 64-bit integer, generated aside hashing the undertaking.
I did an considerable testing with randomly-generated strings and not dash a smash-up after millions of anomalous words. Well, there is nothing worse that unnatural investigation meaningfulness, I conjecture.
I’m performing a earnestly cash in the search motor so that it see fit acquisition a progressive 32-bit integer due to the fact that identifying words (and documents).
Also, the WYSIWYG managing editor turned in default to bee a creepy-crawly mother-lode, so I’m not satisfied -away its expected in the next versions (I need 3.1+). It’s a side more complex but it’s required.