jtenner

Steps to prove this: 1. Install jest 2. create a test that uses `expect(someRef).toStrictEqual(anotherRef)` 3. validate the `get` property function on `someRef` is executed. This behavior is by design. If...

I can't deviate from developer expectations. Perhaps make a method on the class instead? ```ts class Foo { __asBar(): Bar { // Make whatever you want to compare here }...

> but this is not ts. how to define the function genericly？and compare the private field By the way, private fields are compared. The problem is that computed fields are...

Again. This testing suite is designed with Web Developer ergonomics and expectations. You can leave this open as long as you would like. Sorry for the inconvenience.

As it turns out, there are operator overloads and simd properties already exist, however, we need to wait for the next assemblyscript version to slice.

The version is sliced. We are going to address this issue in 4.0.0

As it turns out, I didn't address this issue. Going to investigate soon.

This shouldn't be an issue with as-pect. We should probably close it.

I will definitely take a look into this soon. Thanks for the report.

It's funny, I'm still working on this. Don't worry, this is coming soon.