Johann Dirry

read the unit tests. tests are a living documentation that tell you exactly how to use the library.

Tensor calculus is not "totally different". It is just a higher abstraction. The basic rules still apply. Thankfully the book I recommended builds the basics from scratch, so it should...

I would skip matrices completely and go for tensors (#14) instead. This would make sense since scalars, vectors, and matrices are just a special kind of tensors.

the lack for matrices and tensors is annoying. it is currently not possible to solve system of equations symbolically: ```fsharp let burger = symbol "burger" let pommes = symbol "pommes"...

I guess the problem is, that it is a numeric calculator and not a symbolic one. So not really a bug.

Here is a variation of the syntax that has been missed in the original proposal (taken from #511): ```csharp public void Foo(object o) requires o is Bar b else throw...

@alrz It probably makes more sense for you to do something like this: ```csharp public void Foo(int age) requires (age > 16) else throw new ArgumentOutOfRangeException("Thou shalt not pass!", nameof(age))...

I disagree with the `where` and `return` syntax. The `where` is already used for type checking. It would be overkill to use it in too many contexts. As for the...

if you want a range operator, consider an extension method: ```csharp public static bool IsInRange(this T value, T start, T end) where T: IComparable { return value.CompareTo(start) >= 0 &&...

@Lexcess contracts may not be attached to the functions/methods/procedures directly, but may be „clued“ on. Consider the following code ([taken from here](https://msdn.microsoft.com/en-us/library/system.diagnostics.contracts.contractclassattribute(v=vs.110).aspx)): ```csharp using System; using System.Diagnostics.Contracts; // implementation [ContractClass(typeof(IArrayContract))]...