You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Lambda in tuple in list on single line changes meaning of code #3278
Please describe here the Fantomas problem you encountered.
Check out our Contribution Guidelines.
Extra information
The formatted result breaks my code.
The formatted result gives compiler warnings.
I or my company would be willing to help fix this.
I would like a release if this problem is solved.
Options
Fantomas main branch at 2025-09-08T06:57:30Z - 31029b1
{ config with
MultilineBracketStyle = aligned }
Did you know that you can ignore files when formatting by using a .fantomasignore file? PS: It's unlikely that someone else will solve your specific issue, as it's something that you have a personal stake in.
The pull request was not created — a fallback review issue was created instead due to protected file changes: #3326
🤖 This is an automated response from Repo Assist.
I've re-investigated this bug on the current main branch (post-PR #3303 lambda refactor). The regression test lambda in tuple in list preserves semantics, 3278 now passes — the bug appears to have been fixed as part of the recent lambda refactor work.
To verify: formatting the original input produces the correct output (the list remains multiline, preventing the lambda from capturing subsequent elements as sequence expressions).
This issue can likely be closed. Would the maintainer like to confirm and close it?
Activity
github-actions commentedon Mar 12, 2026
Stay multiline when list contains tuple with lambda as last element (#…
Fix soundness bug: list/array with tuple+lambda elements collapses to…
github-actions commentedon Apr 1, 2026
Note
The pull request was not created — a fallback review issue was created instead due to protected file changes: #3326
🤖 This is an automated response from Repo Assist.
I've re-investigated this bug on the current
mainbranch (post-PR #3303 lambda refactor). The regression testlambda in tuple in list preserves semantics, 3278now passes — the bug appears to have been fixed as part of the recent lambda refactor work.To verify: formatting the original input produces the correct output (the list remains multiline, preventing the lambda from capturing subsequent elements as sequence expressions).
This issue can likely be closed. Would the maintainer like to confirm and close it?
nojaf commentedon Apr 1, 2026
Closed by #3303
Bump the dotnet-sidecars group with 6 updates (#257)
Bump the packages group with 5 updates (#106)
Bump the packages group with 6 updates (#84)