Roman Knyazhitskiy
Roman Knyazhitskiy
Same issue here, with a clean installation of the newest neovim (v0.9.5) with Python 3.10.12. Would be interested in the support for the newer versions :)
@benlubas, hey! Everything works with Molten, I just forgot to mention that here :)
There are quite a lot of people who encountered this issue when using jaxtyping, which is mostly used in IPython notebooks. For example, [this one](https://github.com/google/jaxtyping/issues/104), or [this one](https://github.com/google/jaxtyping/issues/100). @agronholm, to...
I am quite sure that it is the right issue. For example, you mentioned that somewhen in May: > I'm not very comfortable adding a hack that only works for...
> The `jaxtyping` and `IPython` issues have nothing whatsoever to do with each other. The `jaxtyping` related issue you're probably thinking of is described here: #353. That issue is the...
Coming back to this, it looks like it might take quite a bit of time for beartype/typeguard to standardize their APIs, and implement them, so I think it would be...
I believe that you are right about the reason: it seems most likely that slow compilation time is caused by JAX unrolling the ```for i, eval_point ...``` loop. About your...
@PrathamLalwani, you can find the contribution guideline at [CONTRIBUTING.md](https://github.com/patrick-kidger/equinox/blob/main/CONTRIBUTING.md). For the typechecking you might want to use jaxtyping IPython hooks, something like this: ``` import jaxtyping %load_ext jaxtyping %jaxtyping.typechecker beartype.beartype...
* Hmmm, I think your solution (or it's simple modification) won't force the retracing of ```my_error_if``` on update of the ```global_priority_level```, since the value of ```global_priority_level``` will be baked in...
Huh, interesting. --- Next part is mostly outdated due to Patrick's comment, I had some misconceptions about jaxtyping… Feel free to ignore it :) --- I read about what the...