News for hackers. Stuff that matters.
Re:The Rust Calling Convention We Deserve by pjmlp on Friday April 19, 2024 @08:21AM (#40085883)
Except that is only true since those attributes were introduced in recent .NET versions, and it doesn't account for COM marshaling issues.

Plenty of .NET code still using the old ways that isn't going to be rewritten, either for these attributes, or the new Cs/WinRT, or the new Core COM interop, which doesn't support all COM use cases anyway.

Re:The Rust Calling Convention We Deserve by neonsunset on Friday April 19, 2024 @09:54AM (#40086872)
Code written for .NET Framework is completely irrelevant to conversation since it does not evaluate it.

You should treat it as dead and move on because it does not impact what .NET can or can’t do.

There is no point to bring up “No, but 10 years ago it was different”. So what? It’s not 2014 anymore.

Re:The Rust Calling Convention We Deserve by pjmlp on Friday April 19, 2024 @11:17AM (#40087903)
My remarks also apply to modern .NET, as those improvements were introduced in .NET 6 and .NET 8, and require a code rewrite to adopt them, instead of the old ways which are also available, in your blind advocacy you happened to miss out.

Very few code gets written from scratch unless we are talking about startups.