Conversation
❗ Release notes required
|
Co-authored-by: dawe <dawedawe@posteo.de>
|
Hi @vzarytovskii, if possible could you do the backport thing? Would be nice if this makes it into a patch release. |
Which version? 20x? |
|
Yeah, whatever ships before |
|
/backport to release/dev17.9 |
|
Started backporting to release/dev17.9: https://github.com/dotnet/fsharp/actions/runs/8006597118 |
|
@vzarytovskii backporting to release/dev17.9 failed, the patch most likely resulted in conflicts: $ git am --3way --ignore-whitespace --keep-non-patch changes.patch
Applying: Consider prefixed module name in nameof expression.
Applying: Consider prefixed module name in nameof pattern.
Applying: Remove foo
Applying: Update release notes
Using index info to reconstruct a base tree...
A docs/release-notes/.FSharp.Compiler.Service/8.0.300.md
Falling back to patching base and 3-way merge...
CONFLICT (modify/delete): docs/release-notes/.FSharp.Compiler.Service/8.0.300.md deleted in HEAD and modified in Update release notes. Version Update release notes of docs/release-notes/.FSharp.Compiler.Service/8.0.300.md left in tree.
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0004 Update release notes
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".
Error: The process '/usr/bin/git' failed with exit code 128Please backport manually! |
|
@vzarytovskii an error occurred while backporting to release/dev17.9, please check the run log for details! Error: git am failed, most likely due to a merge conflict. |
|
@nojaf auto-merge failed, could you please cherry-pick it and PR to 17.9? |
* Consider prefixed module name in nameof expression. * Consider prefixed module name in nameof pattern. * Remove foo * Update release notes * Update src/Compiler/Driver/GraphChecking/FileContentMapping.fs Co-authored-by: dawe <dawedawe@posteo.de> --------- Co-authored-by: dawe <dawedawe@posteo.de>
| | SynExpr.Ident moduleNameIdent -> Some(NameofResult.SingleIdent moduleNameIdent) | ||
| | SynExpr.LongIdent(longDotId = longIdent) -> |
There was a problem hiding this comment.
@nojaf I think this may require more cases that can be parsed here and where a module name is allowed. For example, consider this:
nameof GenericType<Module.TypeInsideModule>Maybe I'm missing something, but I thought this would be covered by a separate case in SynExpr.
If that's correct, I'd suggest going through all of its cases and checking what is allowed in nameof.
Description
This is a slight variation on #16550
Checklist
Test cases added
Performance benchmarks added in case of performance changes
Release notes entry updated: