Skip to content

BEP-008/009: Function and Lambda Syntax Design #3231

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
aaronvg wants to merge 1 commit into
base: canary
Choose a base branch
from
Open

BEP-008/009: Function and Lambda Syntax Design #3231

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
6 changes: 6 additions & 0 deletions beps/docs/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,6 +40,12 @@ Below is an auto-generated index of all BEPs.
<tr>
<td><a href="./proposals/BEP-007-mir/"><strong>BEP-007</strong>: Mid-level Intermediate Representation (MIR)</a> &nbsp; <img src="https://img.shields.io/badge/Status-Draft-lightgrey" alt="Draft"><br><br>This proposal introduces a Mid-level Intermediate Representation (MIR) between THIR and bytecode generation in the BAML compiler pipeline. MIR is a Control Flow Graph (CFG) based representation that simplifies the compilation of complex control flow constructs like `match` statements and error handling (`catch` expressions). By lowering high-level constructs into basic blocks connected by explicit jumps, MIR bridges the semantic gap between the tree-structured THIR and the linear bytecode, making codegen simpler, more maintainable, and easier to extend with new language features.<br><br><span style='font-size:0.8em; color:gray'>Shepherd(s): Antonio Sarosi <sarosiantonio@gmail.com></span></td>
</tr>
<tr>
<td><a href="./proposals/BEP-008-function-and-lambda-syntax-design/"><strong>BEP-008</strong>: Function and Lambda Syntax Design</a> &nbsp; <img src="https://img.shields.io/badge/Status-Draft-lightgrey" alt="Draft"><br><br><br><br><span style='font-size:0.8em; color:gray'>Shepherd(s): Language Design Team</span></td>
</tr>
<tr>
<td><a href="./proposals/BEP-009-function-and-lambda-syntax-design-ts-aligned/"><strong>BEP-009</strong>: Function and Lambda Syntax Design (TS-aligned)</a> &nbsp; <img src="https://img.shields.io/badge/Status-Proposed-yellow" alt="Proposed"><br><br><br><br><span style='font-size:0.8em; color:gray'>Shepherd(s): Language Design Team</span></td>
</tr>
Comment on lines +43 to +48
Copy link
Contributor

@coderabbitai coderabbitai bot Mar 11, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick | 🔵 Trivial

Add descriptions for BEP-008 and BEP-009.

Both new BEP entries have empty descriptions (showing only <br><br> placeholders), while several other BEPs in the table include helpful summary text. For two competing proposals on function/lambda syntax, descriptions would help readers quickly understand the key differences:

  • BEP-008: Could note "Proposes unified -> syntax for declarations, lambdas, and types"
  • BEP-009: Could note "Proposes TypeScript-aligned : for declarations and => for lambdas/types"

Since the table header indicates this is auto-generated (line 7: "Do not edit the table below by hand"), you may need to either:

  1. Add description metadata to the BEP README frontmatter or content
  2. Update the generation script to extract summaries
  3. Manually add descriptions if auto-generation isn't fully implemented yet

</tbody>
</table>

Expand Down
Loading
Loading