👋DON'T👋MAKE👋CONSTANTS👋IF👋YOU👋ONLY👋USE👋THEM👋ONCE👋TO👋CREATE👋ANOTHER👋CONSTANT👋

The compiler should neatly optimize that kind of stupidity though.....

Your rant sadly gave me cancer

Look into some kernel headers..bro..When u look into that , you may understand why it makes sense sometimes..By the way ..in those ppl use macro constants..

inb4 constexpr values

Names usually just make more sense than some seemingly random number

Not sure why not?
Lately I use const for everything except for loops which need to be let of course.

I have a bunch of those and it's completely justified. I use them as 'settings' that can't directly be used in the code so they go in another constant that is later used many times.

Well it depends. If you have something like

int one = 1;
double y = x + one;

Then ok, it makes no sense! But if it is a sort of configurable parameter, or something like Math.Pi / 2 (I'm thinking about some trigonometric applications), then why not? It certainly improves readability!

@7Raiden
More like the first case.

Schema='https'
Hoster='some hoster'

Api_destination= Schema + '://' + Hoster

(Sry about the uppercase varnames, but typing code on phone is a pain)

@Awlex ahahah ok that's fine then ;)