Coding 2025-08-23
Why are all of the errors I don't care about mega-verbose, and then when there's something I consider an urgent problem, the details are just like "Error: no"?
Why are all of the errors I don't care about mega-verbose, and then when there's something I consider an urgent problem, the details are just like "Error: no"?
It feels like the other approach should have worked, but I suppose this is cleaner.
Grinding out some Quick and Questionable code.
And suddenly, I'm back over here.
Just have to accept what I feel like working on.
As I go to write this summary, I realize I missed a "failed" node type. I'll get it later, when I know I need it.
I had this locked and loaded for days, so it wasn't a big deal.
The rest of the owl is shaped really weird.
There might be a way to make this code more concise, but right now I have to focus on getting it written.
It's weird that it doesn't like the type, when it's entirely capable of figuring out the return type value.