Coding 2024-12-13
As I look at MOTR's code with fresh eyes, I discover a gap in the typing coverage. This first manifested in some light boilerplate code that I realized wasn't accomplishing anything. And it wasn't accomplishing anything because there's no connection between where it's defined, and where its definition is supposed to propagate to. I'm going to try to fix this, just to see what problems it causes as a result...
Well, the code looks a little weirder, but things should be actually hooked up now, probably...
Well, I managed to inline enough code that my code coverage fell by 0.01%. My hope is that the modules are a little more focused now.
Looking at this code with fresh eyes, one issue that I'm seeing is that different modules are using the same name for a value with different types, but the fact that the type is different may not be immediately obvious. I'm going to have to redo these names.
For now, I'm incredibly tired, so I'll be getting to bed.
Good night.