overlookmotel 2c7bb9f6c8 refactor(ast): pass final ScopeFlags into visit_function (#4283) ... We have a strange workaround for `visit_function` where we pass in `ScopeFlags`, to support creating the scope inside `Function`, but setting different flags for `MethodDefinition`s. Previously `visit_function` took `Option<ScopeFlags>` and then did `flags.unwrap_or(ScopeFlags::empty()) | ScopeFlags::Function` to it. Personally, I found this confusing. When I was looking at `MethodDefinition`, I was wondering "It's a function, why doesn't it set Function flag too?" This changes makes it more explicit and clear what `ScopeFlags` everything has.		2024-07-16 07:22:07 +00:00
..
src	refactor(ast): pass final ScopeFlags into visit_function (#4283)	2024-07-16 07:22:07 +00:00
Cargo.toml	chore: turn off doctest for all [[bin]]	2024-07-14 16:55:19 +08:00