Using replaceable operating system API plugins

[zhuxiujia]

Currently, I see that Mutex locks on Windows using TryAcquireSRWLockExclusive and AcquireSRWLockExclusive. The former only supports Windows 7 and above, while the latter supports Windows Vista and above.

Using the APIs of both resulted in compatibility only with Windows 7 and not supporting Windows XP, Windows 2003, Windows 2008. if you want run this exe will be can't find TryAcquireSRWLockExclusive on kernel32.dll

see this example :

fn main() {
    println!("Hello, world!");
}

What I want to ask is why not move the API called by the operating system to a replaceable plugin, such as the toolchain toolchain in Rust, so This is more flexible, and we can build our own toolchain that is compatible with older versions of the operating system

[AngelicosPhosphoros]

AFAIK, Rust is dropping support of Windows 8.1 soon: rust-lang/compiler-team#651

[han1548772930]

Yes I agree too

[riking]

The rust9x and win7 targets will need to add cfg blocks to backfill compatibility on those old targets. The main Windows targets are now Win10+ only.

The win7 target has no changes to make with SRW locks, of course. You should get in contact with the rust9x mantainers.

[ChrisDenton]

Currently the only way to have different OS configurations is to add a new target (either in tree or out of tree, e.g. rust9x). Fully addressing this will require a few things to happen. RFC 3379 proposes a target_os_version config that could be used to select different function for different versions. However, std is prebuilt for each target so won't be able to make use of it on its own. The build-std project goal hopes to address that.

So closing this in favour of those efforts.