Cache hash value of ImmutableRecord

Due to the data structure to being intended immutable, the hash value cannot change during object lifetime. This commit caches the value upon first evaluation.

A bit puzzled about the CI failure. Did your CI setup change globally somehow?

As of a recent MR, we're also running pylint (in errors-only mode) in addition to flake8. That's what failed.

added 1 commit

• 9cca2d74 - [pylint] fix else-after-raise errors from pylint

Compare with previous version

added 1 commit

• d11b457e - More pylint warnings in lex.py

Compare with previous version

mentioned in merge request loopy!314 (closed)

Loopy test balloon: loopy!314 (closed)

LGTM, will merge once the loopy test balloon passes.

Passed. In it goes.

Thanks for the contribution (and for cleaning up unrelated failures!).

mentioned in commit 754d02f5

merged