Use "unknown" rather than "oblivious" for nullability that is not specified

dotnet / csharplang

The official repo for the design of the C# programming language

11.49k stars 1.02k forks source link

Open cston opened 6 years ago

cston commented 6 years ago

Update nullable-reference-types.md to use the term "unknown" rather than "oblivious" for nullability that is not specified.

The term "unknown" is used in the public API: see Nullable.Unknown.

jcouv commented 5 years ago

We should confirm with @MadsTorgersen first. The spec does talk about "oblivious".

Tagging @cartermp @333fred as well (we may choose to adjust the public API depending on the choice here.

333fred commented 5 years ago

The current API proposal uses Disabled for nullability that comes from a disabled context.

jcouv commented 5 years ago

Started thread with relevant folks. I think Disabled is fine, but just want to confirm and close this issue.

cartermp commented 5 years ago

I'm fine with Disabled as well.

jaredpar commented 3 years ago

Moving to csharlang as this is a spec issue at this point.