Johann Dirry

@Lexcess because of the declaritive approach: I am unsure how something like ```csharp public (string foo, int bar) FooBar() where return foo : NotWhiteSpace, MaxLength(10), HasUnicodeBom16 where return bar :...

@Lexcess my rationale is that functor attributes and higher order functions are harder to implement and harder to do interference with. I prefer the simpler solution in such cases.

@Serg046 *"Why do we need to throw an exception manually each time of usage?"* We don't. Contracts should be enforced at compile time. An error in the build log with...

@Lexcess I find the `where` syntax confusing. `require`, `ensure` and `assert` keywords seem more consistent with established conventions: * [Eiffel: An Introduction to Design by Contract](https://www.eiffel.com/values/design-by-contract/introduction/) * [Spec# Example](https://en.wikipedia.org/wiki/Spec_Sharp#Example)

there is another reason. in cases where the `return` keyword is absent, it would not be clear when the constraint must be satisfied. ```csharp public static class Incrementor { public...

@TylerBrinkley how do you write the following? ```csharp public int Foo(ref int bar) require bar < 3; ensure bar > old(bar); ensure return > 0; { // do something }...

@Lexcess that range constraint doesn't solve the problem. try again.

Haven't had that issue. Can you make a ping to the bridge?

apparently this is still not working in the current PowerShell Core v6.1. any updates on this?

why not use something like: ```csharp using Microsoft.Extensions.Configuration; using Microsoft.Extensions.DependencyInjection; using Microsoft.Extensions.Options; using Splat.Microsoft.Extensions.DependencyInjection; // ... public partial class App : Application { protected override void OnStartup(StartupEventArgs e) { using(var...