Note that the context here is it would be one by default for new projects only. Not existing ones. And there's no errors, only warnings (unless someone makes warnings errors, in which case they are already advanced users).

Major point is that this isn't a feature you just enable in templates and hope it works out

@richlander could you clarify this? The feature has seen a bunch of improvements due to adoption by package authors and some advanced users, but we're pretty much now at the point where we just need more widespread usage. The safest route forward is to enable it for new projects that only depend on the core libraries, and at some point in the future (likely after several releases), for all projects. This would be that next step.

work with package owners to turn on nullable

This has been ongoing, and lots of packages have done so already.

update docs with why/how/what on nullable

We have docs here: https://docs.microsoft.com/en-us/dotnet/csharp/nullable-references

There could perhaps be more on the why, but at the same time, the goal is that reference types distinguish between nullable/non-nullable moving forward. It's not some additional "advanced mode" to turn on. It's just what C# is about moving forward.

create video describing why and how and what

Seems great, but I don't think this is needed for new projects right now.

create migration guide for package owners

We don't have this, but all things nullable (e.g., the attributes package authors care about) are documented. I don't think this is a prerequisite for new projects though.

Enable nullable by default for new projects #485

Description

Metadata

Metadata

Assignees

Labels

Type

Fields

Projects

Milestone

Relationships

Development

Issue actions