Mono gets a stack overflow when trying to run FSharp.Compiler.Service with that enormous file (https://github.com/Microsoft/visualfsharp/blob/44c7e10ca432d8f245a6d8f8e0ec19ca8c72edaf/tests/FSharp.Core.UnitTests/SurfaceArea.net40.fs). Can I throw that literal in a text file and change the test to read it into memory instead?
Because of this issue I can't open FSharp.sln with Rider (I have other issues getting the solution to work with Rider also, but this is the big showstopper right now).
Repro steps
I initially reported it here: JetBrains/resharper-fsharp#23
@auduchinok did more investigation here: mono/mono#11933
Expected behavior
Shouldn't crash.
Actual behavior
Crashes.
Known workarounds
Splitting the file into two literals allows Rider to open the solution, or reading it into memory from a text file.
Mono gets a stack overflow when trying to run FSharp.Compiler.Service with that enormous file (https://github.com/Microsoft/visualfsharp/blob/44c7e10ca432d8f245a6d8f8e0ec19ca8c72edaf/tests/FSharp.Core.UnitTests/SurfaceArea.net40.fs). Can I throw that literal in a text file and change the test to read it into memory instead?
Because of this issue I can't open FSharp.sln with Rider (I have other issues getting the solution to work with Rider also, but this is the big showstopper right now).
Repro steps
I initially reported it here: JetBrains/resharper-fsharp#23
@auduchinok did more investigation here: mono/mono#11933
Expected behavior
Shouldn't crash.
Actual behavior
Crashes.
Known workarounds
Splitting the file into two literals allows Rider to open the solution, or reading it into memory from a text file.