Zig author here. Welcome to the club.
How do you solve the IDE features ("fast and trustworthy refactorability (ie: renaming symbols)") in the presence of conditional compilation?
btw your name is an anagram of "beefitrian"
How do you solve the IDE features ("fast and trustworthy refactorability (ie: renaming symbols)") in the presence of conditional compilation?
btw your name is an anagram of "beefitrian"
It's true that symbols in 'false' preprocessor blocks will not be caught. Maybe it's best said "if the compiler will find the symbol when you compile, then the symbol renamer will find it when you rename". Which is definitely not true for most symbol renames I dare to attempt in C++ IDEs.
I think starting with an IDE from the very beginning was a smart move.
For what it's worth, here is my current vaporware plan to solve this problem: https://github.com/ziglang/zig/issues/3028
I would be curious to see your thoughts on this, especially if you end up trying to tackle this problem in Beef.
They probably want newcomers to try a release, and if intrigued, clone the repo and stay current.
A shorter release cycle wil mean that folks will get new stuff/bugfixes faster and that Zig will get more mindshare in return.