Don Syme
Don Syme
@vasily-kirichenko I'm not sure - I haven't looked closely, particualrly about whether it would be breaking change Erik did some important work in improving things but it looks like we...
> @dsyme @vasily-kirichenko From a production point of view, I think that the value offered by such an addition far outweighs any backward compatibility concerns. Well, FSharp.Core has to be...
@eiriktsarpalis Didn't the ExcceptionDispatchInnfo work on FSharp.Core 4.4.1.0 (?) improve these stack traces for exceptions? Is this a case we missed, or was that work never going to improve this...
@vasily-kirichenko Does applying [this techniqe](https://github.com/Microsoft/visualfsharp/issues/2741#issuecomment-291192169) improve things for this example?
@vasily-kirichenko Just to say I've been getting plenty of difficult stack traces too - both from "async" and "Cancellable". And I'm getting _very_ motivated to do something about it. Here's...
@vasily-kirichenko I've been mulling over what might allow us to make progress on non-exceptional stack traces in F# computation expressions. The vague idea I have is best first explained for...
OK, reopening. As mentioned above much of the impact is reduced by the combination of #513 and the dilegent use of NonStructuralComparison.
@nojaf My initial decision is to agree with this. Please let me know if you think this is wrong or inconsistent.
Great! thank you
@nojaf @auduchinok Do we need a docs update for this?