8:12:38ShinmeraYou can try the snippet yourself, it'll very likely produce a similar error with different code points.
8:13:10ShinmeraBut yeah, all #xFFFF code-points are valid unicode.
8:14:22ShinmeraI stumbled on this because I'm implementing unicode algorithms and want to test my stuff against random garbage attacks. Debugging that without SLDB is... troublesome.
8:19:56luisMy memory is fuzzy but there are some non-characters but it's probably only CCL that's pedant about it.
8:33:36ShinmeraI can't seem to create an example myself though.
8:37:42ShinmeraYeah, all the barfing strings do contain characters in that range
8:37:50ShinmeraBut the char reported as invalid seems... random?
8:49:10luisIt might be the previous character, maybe?
8:49:34ShinmeraIf I try to construct the test it reports the correct character as faulty
8:53:06ShinmeraI don't have time to debug this further. The behaviour is too confusing for me to know what to do at this point
8:54:00ShinmeraIgnoring the invalid range in my constructed examples is good enough for now, but it would be better if Slime either replaced or removed invalid characters when sending stuff over, since the current semi-crashing behaviour is far less than ideal.
8:54:58luisDefinitely. Can you open issue with the test case that does fail?