meetings/2017/LDM-2017-10-25.md
Warning: These are raw notes, and still need to be cleaned up. Read at your own peril!
34 should bot be concurrent safe, just like the other compound assignment.
Bundle with 8.0, but could push out. Seems to align with nullable reference types
Reconcile 32 with 1020
Criteria:
Not currently allowed, should probably have a proposal (Andy)
Push out to 8.0 for realism, but still prioritize design time
These should happen together in 7.3
Keep in 7.3, see if we can settle design
Relatively obvious design, with some gnarly bits (dynamic, conversion)
Usability gap with tuples let's keep it.
Let is more important than from. It lets you use out variables
from s in strings
let t = (b: int.TryParse(out var n), n)
where t.b
select t.n
Could be
from s in strings
let (b, i) = (int.TryParse(out var n), n)
where b
select i
There's a bit of design work, especially if we also want the from clause.
We could allow out vars but not the deconstruction, and it would still be useful.
Could save dec for later. It's actually orthogonal.
Action:
Carve out deconstruction, push to 8.X
On the brink, but keeping for now; need to be convinced of value
Keep pushing on it, got to get the train going on Range
x..y does new Range(x, y) or Range.Create(x, y)
Consider whether it should be a new kind of operator instead.
Micro-feature: Just allow System.Enum as a constraint
Mini-feature: allow enum as a constraint, translate to System.Enum, struct
Keep this in, but it is very cuttable.
It's a zero-conceptual-overhead feature.
Original designers left in space between meanings for a purpose. But that's not so compelling to us anymore.
Because it touches overload resolution, it might be better aligned with a .0 release. But we're not compelled by that.
Let's keep it, but again, it's cuttable.