Remove draft

Author: nojaf

src/sessions/2024-12-13.md

@@ -12,14 +12,6 @@ youtubeId: ""
 
 ## Topic
 
-The F\# language is driven by language suggestions in .
-Placing a suggestion is easy, the hardship is listed in the implementation.
-As we established in some of our past [sessions](../) contributing to the F\# compiler can be challeging.
-And even we you managed to make it work, in open-source, you still need a signoff from the maintainers.
-
-In this session, we will take [dotnet/fsharp/#18049](https://github.com/dotnet/fsharp/pull/18049) as a case study on how a language suggestion was implemented.
-We will try and have a mob PR review session to provide feedback on this large pull request.
-
 The evolution of the F# language is guided by community suggestions submitted to the [fsharp/fslang-suggestions](https://github.com/fsharp/fslang-suggestions) repository. While proposing a new idea is straightforward, the real challenge often lies in its implementation. As we’ve discussed in previous [sessions](../../), contributing to the F# compiler can be demanding. Even after overcoming the technical hurdles, open-source contributions require approval from maintainers to be accepted.
 
 In this session, we’ll examine [dotnet/fsharp/#18049](https://github.com/dotnet/fsharp/pull/18049) as a case study, exploring how a language suggestion made its way to implementation. Additionally, we’ll conduct a mob PR review to provide collaborative feedback on this substantial pull request.