language-specifications

I know where to find the C# 5 Language Specification but I cannot find the C# 6 Language Specification anywhere. Where is the C# 6 Language Specification? At time of writing (May 2016) Microsoft hasn't yet finished updating the spec for C#6. In the meantime, I put up Microsoft's latest current draft of the C#6 spec here: https://github.com/ljw1004/csharpspec/blob/gh-pages/README.md This current draft is almost finished, save for a few remaining TODO comments and checking. (This version has been converted into github+markdown, but it also has links to download DOCX and PDF versions of the spec,

This question already has an answer here: How do foreach loops work in C#? 7 answers How exactly is foreach implemented in C#? I imagine a part of it looking like: var enumerator = TInput.GetEnumerator(); while(enumerator.MoveNext()) { // do some stuff here } However I'm unsure what's really going on. What methodology is used for returning enumerator.Current for each cycle? Does it return [for each cycle] or does it take an anonymous function or something to execute the body of foreach ? It doesn't use an anonymous function, no. Basically the compiler converts the code into something broadly

I was wondering why I can not have generic property in non-generic class the way I can have generic methods. I.e.: public interface TestClass { IEnumerable<T> GetAllBy<T>(); //this works IEnumerable<T> All<T> { get; } //this does not work } I read @Jon Skeet's answer , but it's just a statement, which most probably is somewhere in the specifications. My question is why actually it is that way? Was kind of problems were avoided with this limitation? Technically, the CLR supports only generic types and methods, not properties, so the question is why it wasn’t added to the CLR. The answer to that

Prompted by the discussion here The docs suggest some equivalent code for the behaviour of all and any Should the behaviour of the equivalent code be considered part of the definition, or can an implementation implement them in a non-shortcircuit manner? Here is the relevant excerpt from cpython/Lib/test/test_builtin.py def test_all(self): self.assertEqual(all([2, 4, 6]), True) self.assertEqual(all([2, None, 6]), False) self.assertRaises(RuntimeError, all, [2, TestFailingBool(), 6]) self.assertRaises(RuntimeError, all, TestFailingIter()) self.assertRaises(TypeError, all, 10) # Non-iterable

In C / C# / etc. you can tell the compiler that a literal number is not what it appears to be (ie., float instead of double , unsigned long instead of int : var d = 1.0; // double var f = 1.0f; // float var u = 1UL; // unsigned long etc. Could someone point me to a list of these? I'm specifically looking for a suffix for short or Int16 . Thomas Levesque var d = 1.0d; // double var d0 = 1.0; // double var d1 = 1e+3; // double var d2 = 1e-3; // double var f = 1.0f; // float var m = 1.0m; // decimal var i = 1; // int var ui = 1U; // uint var ul = 1UL; // ulong var l = 1L; // long I think that's