[HttpPost]
public ActionResult Create()
{
    return new StatusCodeResult(StatusCodes.Status201Created);
}

[HttpPost]
public ActionResult Create()
{
    return StatusCode(StatusCodes.Status201Created);
}

🤔

Since your examples pass null as the value as well, you could just use StatusCode or StatusCodeResult.

Now, I have wished for an overload of Created that has value, but not uri. A lot of times when you return back a complete result, it's unnecessary to return the location to the client as that URI would just yield the same result.

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.

Strawman API proposal:

namespace Microsoft.AspNetCore.Mvc
{
    public class CreatedResult : ObjectResult
    {
+        public CreatedResult()
    
-        public CreatedResult(string location, object? value)
+        public CreatedResult(string? location, object? value)

-     public CreatedResult(Uri location, object? value)
+    public CreatedResult(Uri? location, object? value)
    }

    public abstract class ControllerBase
    {
+        public virtual CreatedResult Created()
    
-        public virtual CreatedResult Created(string uri, [ActionResultObjectValue] object? value)
+        public virtual CreatedResult Created(string? uri, [ActionResultObjectValue] object? value)

-         public virtual CreatedResult Created(Uri uri, [ActionResultObjectValue] object? value)
+        public virtual CreatedResult Created(Uri? uri, [ActionResultObjectValue] object? value)
    }
}

namespace Microsoft.AspNetCore.Http
{
    public static class Results
    {
+        public static IResult Created()
    
-        public static IResult Created(string uri, object? value)
+        public static IResult Created(string uri?, object? value)

-        public static IResult Created(Uri uri, object? value)
+        public static IResult Created(string uri?, object? value)
    }
}

I'm not super convinced that making the location/uri parameters nullable is a huge win since you'd need either (string?)null or (Uri?)null to select the right overload. We could also consider adding single parameter overloads that just take the location/uri.

Thank you for submitting this for API review. This will be reviewed by @dotnet/aspnet-api-review at the next meeting of the ASP.NET Core API Review group. Please ensure you take a look at the API review process documentation and ensure that:

• The PR contains changes to the reference-assembly that describe the API change. Or, you have included a snippet of reference-assembly-style code that illustrates the API change.
• The PR describes the impact to users, both positive (useful new APIs) and negative (breaking changes).
• Someone is assigned to "champion" this change in the meeting, and they understand the impact and design of the change.