-
### What kind of issue is this?
- [X] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [ ] babel-plugin-react-compiler (build issue installing o…
-
Hi.
I encountered an error when I tried to compare if two symbolic values are equal. They are expressed as $\frac{-x}{1-(y-z)}$ and $\frac{x}{(y-z)-1}$, which should be equal. But in the following …
-
**Describe the bug**
Upon upgrading to version 0.11.8, we started to get the following error. The issue seems to be in the "elasticstack_fleet_integration_policy". Pinning the version to 0.11.7 resolv…
-
### Is your feature request related to a problem?
At the moment, as far as I can tell, the tensor network objects don't have any implementations for `__eq__`, which results in python using the standa…
-
## do_not_check_equality_to_self
## Description
Checking equality to self will always return true and is likely a typo.
## Details
Although good code tries to avoid it, sometimes two diffe…
-
- collapse `getRecord` and `getRecords` into a single `get` function that has a few optional parameters (e.g. `key` or `keys`)
```ts
// get records
useStash(stash, (state) => get({ state, t…
-
Hi all, just getting into pint now and loving it so far! Ran into the following confusion. What am I supposed to be doing here?
In code I had expected every == to be True.
```
Python 3.11.4 (ma…
-
There are implementations of `operator=` and `operator!=` in the LLDB API classes.
These are not currently bound in `lldb-sys.rs` and they are not made visible to Rust via `PartialEq` impls yet.
-
Version: BasedPyright v1.12.0
```
Cases within match statement do not exhaustively handle all values
Unhandled type: "tuple[bool, bool]"
If exhaustive handling is not intended, add "case _: …
-
https://github.com/ucsd-progsys/liquidhaskell/pull/1578 added reasoning for function equality, but does not take into account equality of the functions domain/range. E.g.,
```
{-@ plus1a :: Int …