Don Syme

This is done, but we need to check pacakges are building in main and then republish

Note that what's been done so far doesn't adjust the package restore behaviour, so we should leave this open and consider doing that separately > and also have these ensure...

@gbaydin XLA is in DeviceType but no particular plans beyond that https://github.com/dotnet/TorchSharp/blob/45056ff4de0791126e56a186777821767033d5d5/src/TorchSharp/Torch.cs#L391 We'd welcome contributions and testing strategies, it's likely very easy to wire this through

Typical failure: ``` TorchSharp: LoadNativeBackend: Initialising native backend TorchSharp: LoadNativeBackend: Try loading torch_cuda native component TorchSharp: LoadNativeBackend: Loading LibTorchSharp TorchSharp: LoadNativeBackend: Loaded LibTorchSharp, ok = False TorchSharp: LoadNativeBackend: Native backend...

To turn on tracing of the load process we used this: ``` open System.Diagnostics let tracer = new ConsoleTraceListener() Trace.Listeners.Add(tracer) ``` To test out one of the load-native-library probes we...

> @dsyme can you please share what is/are TorchSharp.xxNon Core.dll(s) ??? :-) Sound exciting! Just making space for the future - and for a vibrant ecosystem of components provided by...

Closing as the solution in fsx files it to ad the nuget references

@abelbraaksma Thanks for the analysis and detailed repros. > Though this is, I believe, against the policy that inside a class the order ought to be insignificant. Just to note...

@abelbraaksma Yes, good summary. Certainly neither the language spec nor MSDN is clear about this. Could you submit a clarification to the MSDN docs please? (which are open source now).

@abelbraaksma Thanks for checking all these old issues so thoroughly I don't recall a specific change that would have fixed this - but I will close it since you have...