Build order calls produce different scan-results

[Alien2150]

Putting "addKeywords" in different code spots produces different results. Here is JUnit Test that produces different results with 0.6.3. The Second test fails:

class TrieTest {
    @Test
    fun `works`() {
        val trie = Trie.builder()
                .ignoreCase()
                .stopOnHit()
                .onlyWholeWords()
                .addKeywords(listOf("WhatsApp", "Ban me please"))
                .build()

        assertFalse(trie.parseText("Ban me please. I appreciated it").isEmpty(), "failed 1")
        assertEquals(1, trie.parseText("Call me on WhatsApp. Here is my number").size, "failed 2")
    }

    @Test
    fun `bug-report`() {
        val trie = Trie.builder()
                .addKeywords(listOf("WhatsApp", "Ban me please"))
                .ignoreCase()
                .stopOnHit()
                .onlyWholeWords()
                .build()

        assertFalse(trie.parseText("Ban me please. I appreciated it").isEmpty(), "failed 1")
        assertEquals(1, trie.parseText("Call me on WhatsApp. Here is my number").size, "failed 2")
    }
}

[Alien2150]

This was not happening on 0.4.x