Support compiling with std:c++latest using MSVC (fixes #5150)

[QuellaZhang]

Fixes #5150.

[jameslamb]

Sorry for the long delay, we had some CI issues and then needed to focus on a time-sensitive release.

Those things are resolved, and I'm ready to help move this forward. Could you please merge the latest changes from master into this branch? Then we'll be able to provide more of a review.

Thanks very much for your patience, and sorry for the inconvenience.

[QuellaZhang]

@jameslamb, I have updated the branch.

[jameslamb]

Thanks for this!

Based on successful CI jobs, this change looks ok to me...but the passing CI jobs don't prove that it fixes compilation with MSVC using std:c++latest. As I mentioned, LightGBM is using the C++11 standard everywhere: #5150 (comment).

@guolinke @shiyu1994 Are you comfortable with LightGBM committing to continue supporting std:c++latest, as new C++ standards come out and the specific spec referenced by latest changes? (documentation). If so, I think a new CI job using this option should be added as part of this PR, to ensure that future LightGBM doesn't break this support.

If not, and you'd instead prefer to instead just accept targeted patches like this based on reported issues from users, then it's probably ok to not add a new CI job at this time.

[guolinke]

In my opinion, as long as the changes do not break the C++11, I am okay with it.

[StrikerRUS]

cc @AlbertoEAF

[StrikerRUS]

@jameslamb

I think a new CI job using this option should be added as part of this PR

WDYT about using std:c++latest flag in a part of already existing our CI jobs to save CI time? For example, that flag can be added in R-package CI job that runs against MSVC-2022

LightGBM/.github/workflows/r_package.yml

Lines 95 to 101 in 0c0eb2a

	# Visual Studio 2022
	- os: windows-2022
	task: r-package
	compiler: MSVC
	toolchain: MSVC
	r_version: 4.2
	build_type: cmake

[jameslamb]

yeah @StrikerRUS , I'm ok with that!

I think that, based on https://learn.microsoft.com/en-us/cpp/build/reference/cl-environment-variables?view=msvc-170, this could be done by setting

$env:CL = "/std:c++latest"

somewhere. Does that seem right to you?

[jameslamb]

@QuellaZhang I'm ready to work with you on getting this PR merged.

Are you interested in trying to update it to use std:c++latest on the R package's MSVC job as @StrikerRUS suggested? If you don't have the time or interested (or if I don't hear back from you in the next few weeks), I'll open a separate PR with these changes + the testing changes.