This is probably the single biggest naming problem in our entire code base. All the code HDT wrote calls it "hdt_mihigan" but we have used val in a lot of places. Accepting that it's called hdt_michigan in code is the far easier option, and so we could go forward with this convention. We can still cal it val casually in that case. Or we can use val in code going forward, and eventually drop or rename places it was called hdt_michigan. I'm personally in favor of keeping hdt_michigan but I could be convinced otherwise.
This is probably the single biggest naming problem in our entire code base. All the code HDT wrote calls it "hdt_mihigan" but we have used val in a lot of places. Accepting that it's called hdt_michigan in code is the far easier option, and so we could go forward with this convention. We can still cal it val casually in that case. Or we can use val in code going forward, and eventually drop or rename places it was called hdt_michigan. I'm personally in favor of keeping hdt_michigan but I could be convinced otherwise.