Tanner Gooding
Tanner Gooding
> The first recorded failure was in https://github.com/dotnet/runtime/pull/100993 and the second was in a rolling build with that commit in it so I wonder if we're hitting a new path...
It's worth noting that most APIs exposed in the BCL are functionally "user-defined" and the language has no integrated knowledge of them. For something like `(int)Math.Round(Double, MidPointRounding)`, all it really...
The exact remark should probably be something implying “may” rather than “does”. There are many possible runtimes and a valid implementation of ScaleB may defer into the C runtime, be...
To the extent that the official `LLVM-C` bindings allow you to, yes. LLVM-C (and therefore LLVMSharp) cover most of the core APIs you need. However, it is ultimately not as...
LLVM-C exports it as `LLVMGetExecutionEngineTargetMachine` and corresponding APIs that take `LLVMTargetMachineRef` LLVMSharp exposes this as a "raw API" `LLVM.GetExecutionEngineTargetMachine` and as helper method on the `LLVMExecutionEngineRef` type (in turn, APIs...
> But it doesn't have a managed wrapper. The managed wrapper is very much a WIP and not everything has been exposed yet. Contributions are more than welcome to help...
This is an issue elsewhere in the pipeline. The source doc comments do correctly specify the underlying `T` where relevant: https://source.dot.net/#System.Private.CoreLib/Vector128.cs,257
Was going to come here and open an issue as well. `?.` for reference types in C# does not use `operator ==`. It is equivalent to using `is null` or...
If there's need for the IEEE 754 `Decimal128` type purely as an interchange type, that is itself feasible to add in .NET 9 It just isn't in scope to add...
Resolved with https://github.com/terrafx/terrafx.interop.windows/pull/354