File Scoped Namespace Class

[viniciusxdl]

C# is a wonderful language and I really love it so much, and something that I particularly like a lot is that it is a language that, in addition to being extremely powerful, does not stop in time and is always bringing new features, facilitating how we code and not getting stuck. behind new languages.

Something simply incredible were the top-level instructions, where instead of having to do something like:

using System;

namespace MyApp;

public class Program
{
    public static void Main(string[] args)
    {
        Console.WriteLine("Hello Word!");
    }
}

You can do just this:

Console.WriteLine("Hello Word!");

With that in mind, something I would like to suggest a new feature for a few reasons:

• Make it even easier and generate familiarity for new developers who came from other languages.
• Be useful for the class and file model that is generally widely used.
• Decrease a recoil.

It would be something like File Scoped Namespace but for classes. When used, only 1 class and 1 namespace could be defined in the entire file:

Example 1:

Visual Studio 2022

Code

namespace public class MyApp.Pages.Index;

public override Task OnInitializedAsync()
{
    // ...
}

public override Task OnParametersSetAsync()
{
    // ...
}

Example 2:

Visual Studio

Code

namespace public class MyApp.Pages.Index;

[Paramater]
public string Code { get; init; }

public override Task OnInitializedAsync()
{
    // ...
}

Example 3:

Visual Studio

Code

namespace public class MyApp.Code;

public Code(string code)
{
    // ...
}

public decimal GetDecodeResult()
{
    // ...
}

Separate namespace and class

Another suggestion, if it is better to separate namespace and class:

Visual Studio

Code

public class Code with namespace MyApp.Models;

public Code(string code)
{
    // ...
}

public decimal GetDecodeResult()
{
    // ...
}

Or until:

Visual Studio

Code

namespace MyApp.Models with public class Code;

public Code(string code)
{
    // ...
}

public decimal GetDecodeResult()
{
    // ...
}

Translated by Google Translate.

EDIT:

It ends up simplifying the language a lot, especially for beginners, by linking each class per file, making it more user-friendly, for example:

No namespace

Example.cs

class Example;

public string GetExample()
{
}

Program.cs

var example = new Example();

Console.WriteLine(user.GetExample());

With namespace

Example.cs

namespace class MyApp.Example;

public string GetExample()
{
}

Program.cs

using MyApp;

var example = new Example();
// Or:
var example = new MyApp.Example();

Console.WriteLine(user.GetExample());

The teaching is much better.

[sharpchen]

I don't see any benefit in this; it only eliminates two curly braces and one indentation level. An analyzer might be more suitable than a language feature for enforcing one type per file.

[viniciusxdl]

@sharpchen

It ends up simplifying the language a lot, especially for beginners, by linking each class per file, making it more user-friendly, for example:

No namespace

Example.cs

class Example;

public string GetExample()
{
}

Program.cs

var example = new Example();

Console.WriteLine(user.GetExample());

With namespace

Example.cs

namespace class MyApp.Example;

public string GetExample()
{
}

Program.cs

using MyApp;

var example = new Example();
// Or:
var example = new MyApp.Example();

Console.WriteLine(user.GetExample());

The teaching is much better.

[333fred]

Duplicate of #928.