I suspect that this whole "checking if the current list equals a preset" thing is computationally super expensive and slow and not that useful and prevents meaningfully defining reusable lists and all, so maybe instead it's a good idea to rethink how this all works.
(Maybe postpone this to v3.1.0?) done
(Also: Call them "words"? Or just call it "dictionary" or "list" or sth? Because it doesn't have to be a literal word!)
Now that #464 has been implemented, this issue can be postponed to v3.1.0, because any incompatibilities that the word preset migration would require can be made backwards compatible using the framework for #464.
I suspect that this whole "checking if the current list equals a preset" thing is computationally super expensive and slow and not that useful and prevents meaningfully defining reusable lists and all, so maybe instead it's a good idea to rethink how this all works.
(Maybe postpone this to v3.1.0?)done(Also: Call them "words"? Or just call it "dictionary" or "list" or sth? Because it doesn't have to be a literal word!)