Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 21 additions & 0 deletions src/sessions/2024-12-13.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,21 @@
---
title: 'A F# Compiler Tour: Reviewing "Scoped Nowarn"'
preview: 'A F# Compiler Tour: Reviewing "Scoped Nowarn"'
isDraft: true
date: 2024-12-13T14:00:00.000Z
slug: "2024/11/22"
champion: "Martin"
zoomLink: "https://us06web.zoom.us/j/86109507433?pwd=qc6GJtAjXynXVBUE7puI4RwcbOQBI4.1"
zoomPasscode: "review"
youtubeId: ""
---

## Topic

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.

## Champion

- [Martin](https://github.com/Martin521)
Loading