2 ms·
The big news here is they've replaced LLVM with MSVC's backend.
by pornel 16d ago
The big news here is they've replaced LLVM with MSVC's backend.
- booi 16d agoI'm sure that's a requirement for being a "Tier-1" language.
- monocasa 16d agoEh, they call TypeScript a tier 1 language too.
- dartharva 16d agoMSVC always was the default backend for Windows platforms.
- qalmakka 15d agoCodegen was still done via LLVM. LLVM supports the MSVC _runtime_, here they're talking about using their (arguably worse) backend directly to generate code and do optimisations
- qalmakka 15d ago... but why? The MSVC backend has been falling far behind LLVM with every release. I understand they want uniformity but IMHO either they catch up or they switch fully to LLVM, if they can
- pjmlp 15d agoWindows ecosystem, and all those things MSVC backend can do and LLVM does not. For the same reason a Rust frontend is being developed for GCC.
- LtWorf 15d agoWhat are these things?
- pjmlp 15d agoTargeting XBox, Windows drivers in kernel mode, COM interop, structured exception handling, UWP sandboxing,
- LtWorf 15d agoThanks, I wasn't aware. I'm surprised that COM is still a thing!
- pjmlp 15d agoCOM is the main delivery mechanism for Windows APIs since Windows Vista. After the Longhorn reboot all the .NET based APIs were remade in COM, while WinRT introduced in Windows 8, adds a new base interface, replaces type libraries with .NET metadata, and requires an application identity.