Zev Spitz

> any complications in Anthony's proposal. Please clarify what complications you are referring to. Your syntax is irrelevant to this proposal, which discussing aliasing the current variable to the type...

@pricerc > Your example uses an array (that's what {1, 2} is, an array), and converts it to a List, and then passes it as as List: I think it...

I suspect this is why `From` was introduced -- to indicate an array-like literal which the compiler doesn't interpret as an array. It would have been quite possible to have...

> Sorry, I don't understand the "I cannot create it inline" assertion, or how it fits into the OP's example is of a method that takes List(Of T) as its...

> Why would you want to pass arrays to a method that has Lists for parameters? If I have two overloads, one taking a list and one taking an array,...

@jdmichel To add to @KathleenDollard 's comment (_It's not just the declared type..._), if we don't allow flow control to affect the understood type, the only way to use this...

@KathleenDollard > the major special thing about VB is that the code does what it says it is doing - you can see and quickly comprehend that. Today, when I...

@KathleenDollard > if we did this I'd like to fall even deeper into the explicitness Would such a syntax (`Nullable` / `NonNullable`) be extended to value types, leaving two ways...

@jdmichel > I find it (pattern matching) confusing. My mental model of pattern matching looks something like this:  You define a pattern, or set of patterns, and the object...

@pricerc > Although the discussion is nominally about nullable reference types; Is that not really a misnomer, since reference types are by definition nullable? Not quite, although it is a...