Коренберг Марк

Yes, it does. I triggered assertion failure in a library. Please fix documentation about applications, that they should not check corresponding revision in txn responses. And even better, remove these...

I would suggest changing protocol of response if it does not affect old versions of libraries

I did not check, possibly problem also happens if I change deleterange with getrange query.

Using return value of noreturn function is an error, indeed.

@sobolevn please reopen. It's not fixed actually.

The first one. Mypy does not see any errors in using value of noreturn function.

I think, Noreturn must not be compatible with any other type. What the case when it should be compatible ?

Should be `def sys.exit(arg: int) -> Never`. Does not it ? That is the same as `-> NoReturn` here. Both must be incompatible with any other type, like int.

Thanks for verbose explanation. I checked TypeScript: ```ts const sys_exit: (code: number) => never = (code: number) => { throw new Error('message'); }; const x: number = sys_exit(42); ``` It...

Why not make it incompatible with any type to detect obvious errors such as trying to use return value of noreturn functions ?