You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To test this further, I created a Node.js script that hashed words containing every printable character code up to 0xFF. Each word was hashed in a worker thread which was terminated if there was no response after 500ms.
Thank you for releasing such a fantastic library. 😄
In Talisman 1.1.4, the Eudex phonetic algorithm seems to get stuck in an infinite loop when hashing a word containing characters such as [, ] and _.
I discovered this when I hit the [ key by accident whilst experimenting with the Eudex algorithm in the documentation.
To test this further, I created a Node.js script that hashed words containing every printable character code up to
0xFF
. Each word was hashed in a worker thread which was terminated if there was no response after 500ms.Node.js script
Output
The text was updated successfully, but these errors were encountered: