ScalarLike now dispatches to jaxtyping.ArrayLike rather than jax.typing.ArrayLike. This causes better behaviour during docgen.

[patrick-kidger]

No description provided.

[johannahaffner]

Commenting here since it's on topic: I still think that there are some cases where it would be nice to have the more concise expression of jaxtyping ScalarLike. Look at this madness - no one can read that anymore:

[johannahaffner]

To err on the side of caution, we could introduce this only for Scalar and ScalarLike and add a reference that points to the union of types they express. A little info box could go on the pages for searches and descents, since this is where we mainly run into that problem (there is currently only one solver that takes a parameter like this at initialisation - this is IndirectLevenbergMarquardt).

[patrick-kidger]

Youch! This is indeed pretty rough.

That's not intended though -- it should display as just the string ArrayLike:

jaxtyping/jaxtyping/__init__.py

Line 164 in 682787f

if getattr(typing, "GENERATING_DOCUMENTATION", False):

Something's clearly going wrong there 😅

[johannahaffner]

Oh sorry for the false alarm! I had double checked that I'm on jaxtyping 0.2.38, from two weeks ago, and verified that his PR was also accepted two weeks ago - it is just not yet in the latest release, and I missed that.

Anyway, you did good fixing that behaviour 😃