Brad Richardson
Brad Richardson
I guess that means we need to get PR #507 merged in sooner rather than later.
I'm not as familiar with that debug output, so @urbanjost will have to correct me if I'm wrong, but I'd say it looks like it confirms @LKedward's theory. The next...
I'm also in favor of enforcing (with a light touch if possible, i.e. optional) a one module per file and naming convention rule, as it seems like a pretty clear...
I would definitely be in favor of using an automated tool to format the code. As you mention it could save a lot of time dealing with and arguing about...
My vote on empty lines would be to remove consecutive ones, so never have more than 1 blank line as a separator.
Good point @LKedward , I agree.
> The way it can work is that the formatting is applied (but not committed) before running CI tests, to ensure that the CI tests actually work after applying the...
I kind of like the idea of preprocessor variables for this use case.
I think Cargo probably deals with this through their "features" capability and custom build scripts. I'm not quite clear on the design of that capability though, or how well it...
I’m of the opinion we should enforce this only on the “publishing” side, once we finally have an official registry/repository. I wouldn’t want a new user to get confused about...