Improve vector growth performance near max_size

[Arzaghi]

Fixes #1217

As @BillyONeal suggested here I think in the described situation, it is more reasonable to grow the vector to the maximum possible size according to the geometric growth speed.
Furthermore, if someone repeatedly increases vector size it is more likely that he/she wants to increase the size even more. So it is better to have the maximum preallocation space that prevents huge relocating data.
So I've changed it to max_size()

[mnatsuhara]

Would you be interested in finding other affected places in the repo and implementing similar fixes there? (As @BillyONeal mentions in the issue, the same pattern is likely present in other places implementing geometric growth.) If you would rather not, we should probably file a subsequent issue to follow up on other occurrences after vector is fixed.

[Arzaghi]

Would you be interested in finding other affected places in the repo and implementing similar fixes there? (As @BillyONeal mentions in the issue, the same pattern is likely present in other places implementing geometric growth.) If you would rather not, we should probably file a subsequent issue to follow up on other occurrences after vector is fixed.

Yes, I would. I will apply your suggestion on this change and fix other containers for the same issue.

@mnatsuhara Sorry I couldn't find anywhere else contain a similar issue. could you provide a clue about where else should I apply this fix?

[StephanTLavavej]

basic_string already clamps to max_size:

STL/stl/inc/xstring

Lines 4257 to 4269 in 484fbc9

	_NODISCARD static size_type _Calculate_growth(
	const size_type _Requested, const size_type _Old, const size_type _Max) noexcept {
	const size_type _Masked = _Requested | _ALLOC_MASK;
	if (_Masked > _Max) { // the mask overflows, settle for max_size()
	return _Max;
	}
	if (_Old > _Max - _Old / 2) { // similarly, geometric overflows
	return _Max;
	}
	return (_STD max)(_Masked, _Old + _Old / 2);
	}

After a quick search, I also don't see any other occurrences of geometric growth that need to be changed. (valarray grows exactly.) I searched for "geometric", "exponential", and \w+ \+ \w+ / 2. So I think this is sufficient, no need for a followup issue.

[StephanTLavavej]

Thanks for making our vector behavior consistent with string! 🎉