Transparent Compiler returns no completions after a dangling dot
Los mantenedores suelen responder en 3 días
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Aptitud para principiantes
- 72/100
Línea de trabajo
Run ./run.sh to reproduce the difference between the transparent and default compilers. Start in Harness, where ParseAndCheckFileInProject and GetDeclarationListInfo are called, and use Library/Questions.fs and Library/Use.fs as the minimal case. Done means the transparent compiler returns the two expected completions after Questions. without requiring an unrelated reference to Questions.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Hello,
While working on a project of mine I discovered some strange behavior in the intellisense results.
After some investigation, here is what I found:
Investigation# Transparent Compiler returns no completions after a dangling dot
With the transparent compiler enabled, GetDeclarationListInfo returns an empty list for Questions. when Questions is a module declared in an earlier file of the project and the namespace holding it declares no type of its own.
The default background compiler returns the expected list for the same input.
Reproduces on FSharp.Compiler.Service 43.9.300, 43.10.103, 43.12.400, and 43.1001.125 (the build shipped in FsAutoComplete 0.83.0).
Run
./run.sh
transparentCompiler=false 2 completions [|"singleton"; "count"|]
transparentCompiler=true 0 completions [||]
Pass -p:FcsVersion=43.9.300 to run.sh to use a different FCS build.
Input
Library/Questions.fs
namespace Demo
module Questions =
let singleton = 1
let count = 2
Library/Use.fs
namespace Demo
module Use =
let f () =
Questions.
()
Use.fs has one parse error, FS0599: Missing qualification after '.'. The harness asks for completions at the end of the Questions. line.
Observations
Editing Library/Questions.fs and rerunning gives:
Questions.fs shape |
default | transparent |
|---|---|---|
| namespace holds only the module (as checked in) | 2 | 0 |
a type added to the namespace, after the module |
2 | 2 |
a type added to the namespace, before the module |
2 | 2 |
a type added inside the module |
3 | 0 |
Writing Demo.Questions. in Use.fs instead of Questions. changes nothing.
These are correct under both compilers, so the failure is not general to the dangling dot:
- a module declared in the same file as the dot
- an FSharp.Core module, such as
String. - a .NET type, such as
System.Console. - an instance member, such as
s.on astring
Adding an unrelated statement to f does not help. Adding one that mentions Questions does:
let f () =
Questions.
Questions.singleton |> ignore
()
With that line present the transparent compiler returns the 2 expected completions.
Effect in an editor
FsAutoComplete passes --use-fcs-transparent-compiler when the VSCode setting FSharp.fcs.transparentCompiler.enabled is true.
Typing a dot after such a module then offers nothing.
Layout
Library/- the project being analysed. ItsDumpFscArgstarget writes the compiler arguments of a design-time build toLibrary/obj/args.txt.Harness/- console app that callsParseAndCheckFileInProjectandGetDeclarationListInfoagainstLibrary, once per compiler.run.sh- runs the target, then the harness.
fcs-transparent-completion-repro.zip
Related information
Provide any related information (optional):
- Operating system: Omarchy (Arch Linux based), kernel 7.2.3-arch1-3, x86_64
- .NET Runtime kind: .NET (Core)
- SDK 10.0.102, harness and repro project both target
net8.0and run on .NET 8.0.19 - Installed runtimes: 6.0.36, 8.0.19, 9.0.11, 10.0.0, 10.0.1, 10.0.2, 10.0.8
- SDK 10.0.102, harness and repro project both target
- Editing Tools: VSCode 1.137.0 with Ionide-fsharp 7.31.1 (FsAutoComplete 0.83.0), setting
FSharp.fcs.transparentCompiler.enabledset totrue - FSharp.Compiler.Service: reproduces on 43.9.300, 43.10.103, 43.12.400, and 43.1001.125 (the build inside FsAutoComplete 0.83.0)
- Lenguaje dominante
- F#
- Estrellas
- 4.3k
- Forks
- 880
- Merge medio
- 4 d 14 min
- PR fusionados (30 d)
- 99
Preparar el entorno
Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de dotnet/fsharp
-
Semantic classification cache for opened documents is never populated (written to the unopened-documents cache)Posiblemente ocupada @xperiandri la tomó hace 37 días. AbiertoNeeds-Triage
Dificultad 1/5 Menos de una hora Aptitud para principiantes 90/100
Los mantenedores suelen responder en 3 días
-
Needs-Triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
dotnet/fsharp#20265 · 1 comentario ·
Los mantenedores suelen responder en 3 días
-
Bug Needs-Triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Los mantenedores suelen responder en 3 días
-
Question about changed behavior of string interpolations in NativeAOT in the .NET 11 rc1 SDKAbiertoBug Needs-Triage
Dificultad 4/5 Más de una semana Aptitud para principiantes 18/100
Los mantenedores suelen responder en 3 días
-
Caches.Cache: its finalizer keeps a dropped check alive for one more full GC, and MailboxProcessor-mode caches are never collectedPosiblemente ocupada @majocha la tomó hace 1 día. AbiertoNeeds-Triage
Dificultad 4/5 3-5 días Aptitud para principiantes 18/100
dotnet/fsharp#20756 · 2 reacciones ·
Los mantenedores suelen responder en 3 días
Todos los issues de dotnet/fsharp
Issues similares
-
bug derived types format I/O medium priority semantics
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Los mantenedores suelen responder en 1 día
-
lexer: a lone `"` at the end of a file panics instead of reporting an errorPosiblemente ocupada Un pull request vinculado a esta issue está abierto o ya se fusionó. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
bytecodealliance/wasm-tools#2768 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
antlr/grammars-v4#5035 ·
Los mantenedores suelen responder en 5 días
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
Los mantenedores suelen responder en 1 día