This should at least have ascii mentioned in the name. However I'd suggest we do something else. I never got the time to upstream it but I think these things should be put in an Char.Ascii submodule.

If at least two dev team member tell me they would ok with the module I linked above, indicating if possible what they disagree¹ with upfront, I could take the time before the next freeze² to upstream it.

Note that all of these functions remain useful in an Unicode dominated world, because that world dominates in UTF-8 (notably in command line tool outputs) and all of these functions work with the purported ASCII semantics on UTF-8 aswell and remains widely useful.

If at least two dev team member tell me they would ok with the module I linked above

Personally, I would be in favor.

I would indeed prefer to have such a Char.Ascii module ! I'm leaving this open for now until a new PR is opened.

I tend to agree that having a submodule for ascii property might be a good idea, since there are probably other "ascii-property" function that we might wish to add (is_letter? is_whitespace?).

I read too fast @dbuenzli's proposal previously, but after reading the proposed Ascii submodule, upstreaming it does sound like a good idea to me.

Ok I'll look into that in the upcoming weeks. Thanks for the calendar update.