I give up, min / max just doesn't fit my brain

[celes]

It's very common when writing game code to want to express the idea that this variable saturates at a certain value, for example:

Code: Select all

this.x += Time.deltaTime;
if (this.X > maxValue) {
    this.X = maxValue;
}

Now you see how my brain likes to think in terms of the "maximum value" this variable is allowed to have, so trying to get more concise code, I reach for the aptly named....

Code: Select all

this.x = Min(this.x + Time.deltaTime, maxValue)

Min, yes, I have to use min to set a max value and max to set a min value. This breaks my brain, I've known for years, and I still have to stop and think about it every time.

I give up, I'm throwing the towel, I have defined these functions and will be using them from now on

Code: Select all

float AtMost(float a, float b) => Min(a, b);
float AtLeast(float a, float b) => Max(a, b);

[Kampffrosch]

I can deal with

Code: Select all

min(a,b)

but I always read

Code: Select all

a.min(b)

as "a should be at least b"

[celes]

I always read

Code: Select all

a.min(b)

as "a should be at least b"

Yes, the method syntax makes min/max far worse. But at_least / at_most would read so nice in method syntax... I'm gonna add this and see if I end up using it!

[Sugui]

I have another suggestion!

Code: Select all

clampMax(x, to) = min(x, to)
clampMin(x, to) = max(x, to)

... or even

Code: Select all

clamp(x, min=Float.MIN_VALUE, max=Float.MAX_VALUE) = clamp(x, min, max)

so you can write

Code: Select all

this.x = clamp(this.x + Time.deltaTime, max=maxValue)

[celes]

... or even

Code: Select all

clamp(x, min=Float.MIN_VALUE, max=Float.MAX_VALUE) = clamp(x, min, max)

so you can write

Code: Select all

this.x = clamp(this.x + Time.deltaTime, max=maxValue)

Ohhhh I read this before during the stream and didn't realize what you meant. You mean clampMax for min and clampMin for max! Yeah that's cool