This was planned and uucp was explicitly designed with that feature in mind but put on hold because both 4.02 took longer than expected and because I couldn't get proper documentation out of it see #6472.

Besides I didn't commit to a formal policy on ocaml version constraints yet, but I have something in mind like support the current major minus one or two. So that won't happen immediately, but it will eventually.

Also I have to admit that I'm a little bit disappointed by module aliases since they don't really solve the namespace problem but rather multiply the number of visible names without solving the fundamental problem of toplevel names; I do hope however that opam-doc will allow us to hide some of these names in the documentation.

Maybe you should revisit this. Anything using notty starts at about 7.5 MB in size.

This, while agreeing that aliases multiply names instead of solving namespacing.

@dbuenzli pingu

Cute.

Any plans here?

#2 (comment)

This was planned and uucp was explicitly designed with that feature in mind
[...]
So that won't happen immediately, but it will eventually.

That was over a year ago. Do you have any more concrete plans, that you can commit to?

That was over a year ago. Do you have any more concrete plans, that you can commit to?

I fully commit to the plan outlined in that comment. If you are not able to read what is written there it is basically wait that 4.03 is out, and see if it the documentation problem is solved.

Besides in which context are these 7.5mo a problem ?

In the context of the entire Unicode character database being grafted onto executables which display a progress bar. It makes me uncomfortable even expressing the idea to people.

Now, even for a pretty comprehensive Unicode treatment, I only need Break (directly and via uuseg), Gc (via Break and uuseg), and White (uuseg). Compiled data for these three comes to about 1MB, something I'm far more comfortable with imposing downstream.

Friendly ping. Six years later, what is the status of this?

I'll consider doing this for the next Unicode release.

I'll consider doing this for the next Unicode release.

Thanks!

Thanks @dbuenzli!

Well that was a long wait 😬.