Owen Avery

Empty ```TupleStructPattern``` assumed to be function call

2

I tried this code: ```rust struct S(); pub fn main() { match S() { S() => {} } } ``` I expected to see this happen: no error Instead, this...

This adds an extra compiler pass called ```SizedChecker``` which handles the new checks

Fix #2667

5

This also involves some changes to ```get_location``` and ```get_node_id``` method implementation, but I'll probably split those off into separate pull requests. Fixes #2667

It would be nice if we optimized the layout of enums like [rustc](https://doc.rust-lang.org/std/num/struct.NonZeroU8.html) does

Quick fix for ```MacroRuleDefinition``` use-after-free

3

Macro expansion seems to destruct instances of MacroRulesDefinition in modules. This patch should prevent a use-after-free by cloning and then leaking MacroRulesDefinition instances.

Unnecessary (?) ```TREE_SIDE_EFFECTS``` and ```TREE_READONLY``` usage

2

https://github.com/Rust-GCC/gccrs/blob/cfc51d46fcdb70bde84f030557c96866f3b18e23/gcc/rust/rust-gcc.cc#L1491-L1493

these errors would still be nice as hints, but that's outside the scope of this PR. but something aggregating all macro arm misses and displaying them to the user could...

Check for writes outside of the build directory

6

I noticed that ```libgrust/libformat_parser/target``` was seemingly generated outside the build directory on my machine. This should detect similar issues, and confirm/deny the aforementioned issue.

These were leftover from an earlier refactor