This problem is significant.
Fits well with the language. It will remove some pain points.
The nesting optionality of Swift is something I have only used in swift. It is a weird feature that in my experience has only given me problems. I do not recount a single instance where in my code I ever wanted nested optionals. Dictionaries is another area where nested optionals are not very useful.
I greatly desire a generic level feature where I can specify that I only ever want one level of optionality.
The progressive improvement in this area is something that I welcome. I would like to hear from the core team on any plans for explicitly being able to enforce optionals with no optional nested values.
I read the proposal and followed previous discussions lightly.