henry

@panarch @genieCS if there is no more progress, may i take this?

> Sorry for the late review. Could you please resolve the conflict? In general, the changes look good, but the `table_name == $Dummy` side could be improved. ex) The type...

Is there any progress to figure out?

I realized that it was cuz of reserved keyword `User` which is not parsed as `Table`. Anyone knows which PR implement reserved keyword `User`? And What about change the error...

Did you mean selecting 360,000 (100 * 60 * 60) rows from sled storage took 2.7 seconds or 1 row from 360,000 rows?? Did it include client latency to get...

Do we have to implement `get_iterable_element_type` from scratch including all functions related with iterable like `get_next_value_type_of_iteratable`?

Let me try this issue! Is it right way to return Type::Tpl instead of Type::Array in Type::Interface.extends?

@kdy1 Yes! I'm still working on it at local! i will push to github first.

``` $ ./scripts/test.sh arityAndOrderCompatibility 2 unmatched errors out of 17 errors. Got 5 extra errors. Wanted: [RefError { line: 19, column: 5, code: "TS2741" }, RefError { line: 22, column:...

I'm trying to solve [nested_assignment error](https://github.com/dudykr/stc/actions/runs/3729484189/jobs/6325442576) in advance of undraft but cannot get which part is wrong yet.