Don Syme
Don Syme
Close/open to re-run CI
Yes, agreed this is a bug
@daz10000 Could you write out a step by step to recreate the cryptic problems mentioned? Thanks
I don't know of any intrinsic reason - we can't revert a change from that long ago but please do submit a PR to address this if you can
Yes this difference in encoding for type references in attributes has been a bane to rewriting tools before, it is certainly the problem here
I think it is the rewrite phase in the compiler for generated assemblies which is missing this. I'll take a look if its a simple fix (though will take a...
If you have profiling tools you might want to profile the execution of `fsc.exe` compiling this file, and show the top inclusive and top exclusive methods?
@cartermp @kevinransom I'm concerned that the `#r "nuget: ..."` package referencing of package containing type providers is not setting TypeProvideConfig's ResolutionFolder correctly when actually instantiating the type providers. It should...
The F# fix is here: https://github.com/dotnet/fsharp/pull/10866 Until then you should set ResolutionFolder explicitly when using the FSharp.Data type providers with relative resources.
> Am I correct that the ResolutionFolder workaround does not work for CsvProvider.Load? That's correct, that's a runtime behaviour setting, you'll need to do what you did