An original discussion started in the dotnet/fsharp as issue #11370 and has a detailed proposal description and a number of comments.

Pros and Cons

An advantage of making this adjustment to the core library is giving library users freedom to choose in which threading context MailboxProcessor will be started, rather than limiting them to the Async.Start. It also makes MailboxProcessor slightly more efficient in some cases, e.g. when running synchronously, avoiding context switching overhead. The change is trivial, fully backward-compatible, and enables using MailboxProcessor in more contexts.

Extra information

Estimated cost (XS, S, M, L, XL, XXL): XS

Please see it implemented in the PR 11417.

Affidavit (please submit!)

Please tick this by placing a cross in the box:

• This is not a question (e.g. like one you might ask on stackoverflow) and I have searched stackoverflow for discussions of this issue
• I have searched both open and closed suggestions on this site and believe this is not a duplicate
• This is not something which has obviously "already been decided" in previous versions of F#. If you're questioning a fundamental design decision that has obviously already been taken (e.g. "Make F# untyped") then please don't submit it.

Please tick all that apply:

• This is not a breaking change to the F# language design
• I or my company would be willing to help implement and/or test this

For Readers

If you would like to see this issue implemented, please click the 👍 emoji on this issue. These counts are used to generally order the suggestions by engagement.