BenBE
> Thanks for helping me out @BenBE also i had to ask if there's any way to solve all the checks Have you tried compiling this locally? From the build...
This change alone doesn't do anything except show some text. There's code missing to actually handle these two keys. Also on the note re checkboxes: They already react to Space...
The actual change looks good (should be one commit though, not two), but I'm not very eager about the feature overall. @fasterit @natoscott What do you think?
I cleaned up the history (squashing the merge + amended commit). AFAICS only one fork (that I follow/fetch) pulled that commit by the time I force-pushed the updated tip.
I'm neutral either way …
Using `us` instead of `µs` was suggested in my comment mostly for two reasons: 1. Avoids distinguishing cases in the code whether Unicode is available or not. 2. Avoids issues...
Is using the library doable in a way that makes runtime binding to this library feasible? Or would this have to be a compile-time `configure` option?
How stable is its API? Or will we be chasing API change after API change for this lib?
TL;DR: SNAFU. ;-) I already heard not to much good about ICU, thus it didn't surprise me, that ICU4U suffers similarly. For non-UTF-8 encoding you'd thus basically have to go...
> > Fails CI: > > ``` > > XUtils.c:426:6: error: 'HAVE_STRNLEN' is not defined, evaluates to 0 [-Werror,-Wundef] > > 426 | # if HAVE_STRNLEN > > | ^...