bernardosulzbach / advent-of-code Goto Github PK

This should have been done from the start.

There's a travis-ci branch that has some WIP towards this. Travis CI only has old Ubuntu, so all compiler versions available there (of both GCC and Clang) are much older than what I'm using locally and thus cannot build the code in this repository. For instance, they don't support concepts.

We should be able to generate a checklist based on source code for which solutions we already have.

This helps me see which days (or parts) are slowing the whole suite down.

Clippy

Sometimes it’s nice to have an experienced advisor by your side… giving you tips on best practices as you code. That’s what Clippy does —it reviews your code as you go and tells you how to make that code more idiomatic.

rustfix

But if you have an older code base that uses outmoded idioms, then just getting tips and correcting the code yourself can be tedious. You just want someone to go into your code base and make the corrections.

For these cases, rustfix will automate the process. It will both apply lints from tools like Clippy and update older code to match Rust 2018 idioms.

Taken from this blog post.

This will require rewriting history, but it's fine.

We will need 3-dimensional points for 2020-17.

I don't like the language's implicit conversions, and at least GCC can warn about them (when they're unsafe), so we should gradually roll this out to all C++ projects.

Many of the programs, I believe, have unnecessary includes.

We can always remove it later.

As many as 50 files will eventually do part == 1 || part == 2. Should use an Interval and have a standard message for this in common.

And so on.

This is better because then Boost will also report the mismatched values, not just a line number.