Revision f6108674d93727fb89236a51ddc947b0f9d7a17d authored by George Necula on 11 April 2020, 15:27:14 UTC, committed by George Necula on 11 April 2020, 16:30:44 UTC
It seems that JAX (and XLA) are a lot more forgiving for index-out-of-bounds,
except for the case when the dimension has size 0. In this case give a similar
IndexError message as numpy, instead of the current one:

   RuntimeError: Invalid argument: Slice size at index 0 in gather op is out
   of range, must be within [0, 1), got 1.:
   This is a bug in JAX's shape-checking rules; please report it!

Issue: #2671
1 parent c4dd1cf
History
File Mode Size
benchmarks
build
cloud_tpu_colabs
design_notes
docs
examples
images
jax
jaxlib
tests
.gitignore -rw-r--r-- 183 bytes
.readthedocs.yml -rw-r--r-- 504 bytes
.travis.yml -rw-r--r-- 1.9 KB
CHANGELOG.md -rw-r--r-- 92 bytes
CONTRIBUTING.md -rw-r--r-- 581 bytes
LICENSE -rw-r--r-- 11.1 KB
LICENSE_SHORT -rw-r--r-- 575 bytes
README.md -rw-r--r-- 19.5 KB
WORKSPACE -rw-r--r-- 2.4 KB
mypy.ini -rw-r--r-- 292 bytes
pylintrc -rw-r--r-- 1.6 KB
setup.py -rw-r--r-- 1.1 KB

README.md

back to top