5 ms·

I've used tuples in the past when a method could fail and I want the error code back or I want the thing. e.g. (string errorCode, Quax result) TryGetAQuax();

• tjalfi 9y ago
  Could you use the System.ValueTuple NuGet package?
  • LandR 9y ago
    Requires 4.6.1
    • garganzol 9y ago
      Also works with .NET 4.5. System.ValueTuple package has .NET Standard 1.0 target which can be effortlessly used by a .NET 4.5 assembly.
• hurricaneSlider 9y ago
  You can :) (Especially with the pattern matching feature) https://github.com/louthy/language-ext https://github.com/louthy/language-ext
• naasking 9y ago
  > Oh, to have Either / Discrimated Unions in C# :( Here you go: https://sourceforge.net/p/sasa/code/ci/dotnet-standard/tree/Sasa/Either.cs https://sourceforge.net/p/sasa/code/ci/dotnet-standard/tree/... You can use it like: Either<string, int> x = 99; if (x.TryCase1(out var s)) ... else if (x.TryCase2(out var i)) ... Only up to 4 cases are included because beyond that, I think you should define a custom type.
  • naasking 9y ago
    Although I should note that C# now supports special casting via the 'is' operator, so you can now just do this: object x = 99; if (x is string s)) ... do something with 's' else if (x is int i)) ... do something with 'i'
    • coldacid 9y ago
      There's also the OneOf NuGet package [1] which I've put to good use in a number of projects. Using `object` and `is` means you can't enforce what types get passed in, nor can you ensure that all possible types actually get handled. [1]: https://github.com/mcintyre321/OneOf/ https://github.com/mcintyre321/OneOf/
      • naasking 9y ago
        I can never justify the use of delegates for pattern matching purposes. It's just way too much overhead, and so would discourage the use of these abstractions.
• gokhan 9y ago
  > when a method could fail and I want the error code back or I want the thing For this use case, I mostly use a Result<T> with .Status, .Messages, .Exception, .Data etc properties.