strager

The bug is still present. Here's a repro: ```javascript function useState() {} const [a, setA] = useState(), const [b, setB] = useState(); ```

Shipped in version 3.0.0.

I think I addressed the MSVC issues by refactoring parse_and_visit_class to use a helper class instead of a bunch of lambda functions. I'm testing with CI to see: 6eb7a7572908bd6d5830e7719aebb096f89e2a5b

MSVC stackoverflowed with my patch. =\

I think the main issue is that, in unoptimized builds, MSVC allocates all locals on the stack irrespective of liveness. So the following code allocates two booleans on the stack:...

I created a tool to analyze stack usage: https://github.com/strager/cppstacksize It seems that calls to diag_reporter::report are expensive for three reasons: * Diagnostic classes cannot fit in a register, thus are...

The SERP table is less comical now thanks to commit 17b7a82dbc1d17c55318c577ba6c93fd6610d025 and PR #843: ![Uploading Screen Shot 2023-01-31 at 1.42.46 AM.png…]()

`C` will never get executed in the following code, so we should mark it as dead code: ```javascript for (A; B; C) { D; return E; } ```

@erlliam Did you manage to make a reduced test case demonstrating the problem?

This is still an issue as of commit 763fd5455de4fbd8aefb32ddaadd7f7e71b94a3c.