That's why in practice, you should avoid declarations like that. Break down the components into separate `typedef`s with descriptive names that are easy enough to understand in isolation. Then combine those stepwise following the same rule.

Agreed. They turned this declaration:

   char (*(*x())[5])()

into this English description:

> declare x as function returning pointer to array 5 of pointer to function returning char

What was really needed was just to disentangle the function declarations, like this:

   x: fn () -> &((&fn () -> char)[5])

I think a visual representation of a concrete instance of the type would probably be a better explanation of c type declarations. At the moment this tool seems more a C gibberish to english gibberish translator.

My immediate reaction isn't "this is so cool and useful for me" but "this might be really useful over traditional speech translation for programmers who can't use their hands". If you know the code but have difficulty inputting it, this might have real value even if it has none for making understanding the code easier.