[Automated] PRs inserted in VS build main-12222.38
Los mantenedores suelen responder en 4 días
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 1/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Necesita aclaración
- Estado de actividad
- Estancado
- Área
- build-system, release
Línea de trabajo
This is an automated Visual Studio build aggregation listing a complete diff and many already-linked pull requests, but it names no repository files or tests. Start by reviewing the complete diff and the referenced pull requests; there is no standalone change or completion criterion described for this issue.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
- Embed F# metadata trimming rules in compiled assemblies
- Stop Debug builds writing
StandardOutput.txt/StandardError.txtinto the project directory - Say why CommitDelayedDiagnostics copies the collection
- Fix enum constraints in recursive groups and improve constraint diagnostics (#14580)
- Make Debug OTLP export opt-in via FSHARP_OTEL_EXPORT
- Test/Transparent Compiler: test that TC reuses check results after project modifications
- Sort the merged property definitions in one array
- Allow optional arguments in indexer setters
- Fix false FS3261 warnings for unions in recursive declarations
- Allow 'reraise' in computation expression handlers
- Preserve outer rethrows in nested runtime async try/with
- Cleanup: use print/printn for simple string literals and drop redundant sprintf
- Add AGENTS.md and Claude Code rules mirroring Copilot instructions
- Fix
NullReferenceExceptioninEntityon unlinked placeholder entities - Reject runtime async Await in ordinary task state machines
- Support multithreaded MSBuild in F# build tasks
- Keep parentheses around nested tuple argument next to named arg
- Implement RequireNamedArgumentsAttribute (FS-1095)
- Avoid emitting FSI multiemit PDBs without debug info
- Fix array and string slicing overflow for extreme bounds
- Enable runtime async via compiler intrinsics
- Ship net10.0 FSharp.Core with the SDK tools
- Stabilize OptimizeClosureIfNotInlined for F# 11
- Emit MethodImpl flags for property accessors
- Fix misleading diagnostics for reordered record fields
- Keep Peek Definition off the main thread
- Fix ref-assembly MVID collisions from truncating signature-hash combiner
- Clarify code comment guidance
- Add proposing-pr-rewrites skill
- Keep unchanged PRs out of the tooling safety agent
- Reduce recurring workflow notification noise
- Allow 60 minutes for state-machine documentation generation
- IL: fix the per-reader string cache sizing
- Typed tree: create a type's augmentation on first use
- FCS: fix races that made the background builder repeat work
- IL: intern the attributes and type references read from metadata
- IL: map the short-lived metadata-only PE reader
- Name resolution: CheckIWSAM only needs the intrinsic methods
- Symbols: add WithNullnessAnnotations to the display context
- Rich text: filter empty parts
start-vs-VisualFSharpSln.ps1: build against the hive's own Roslyn- Add modern F# idiom instructions for Copilot / Claude Code
- Support positional literal assembly attributes
- Share the empty-array singleton for zero-length Array results
- Fix recursive inline member ordering in optimizer
- FCS: add FSharpCheckFileResults.FileSignature
- Remove obsolete static let language feature flag
- Remove always-on RequiredPropertiesSupport flag
- Remove always-on ErrorReportingOnStaticClasses flag
- Add feature-completeness skill (no deferral of useful work)
- Remove always-on DefaultInterfaceMemberConsumption language feature flag
- Make the
ComponentTestschecker tests asynchronous - Avoid the intermediate array allocation in project
OtherOptions - Cache
DocumentDiagnosticAnalyzerresults by version stamp to avoid redundant typecheck on unchanged documents - Guard the stack when checking long sequence expressions
- Order explicit type args by constraint dependencies before unifying
- Inline List/Array higher-order functions and adapt opaque callbacks
- Use
ValueOptionto look up a reference's definition item - Preserve resumable state-machine lowering in Debug
- Optimizer: eta-float InlineIfLambda partial-application arguments to remove closures
- Fix FS0192 Iterate2D from ReflectedDefinition over a recursive value
- Teach expert reviewers to check runtime representation preservation
- Avoid per-call FSharpFunc closure in remapVal member-info remap
- Make zero-based Array2D allocation AOT-clean
- Make agent model defaults configurable and use Sol
- [MicroPerf] Drop accessibility and attribute-scan closures via ListInline
- [MicroPerf] Drop the per-call closure in generic type-argument codegen
- Optimize skill prompts
- Improve FCS docs
- [MicroPerf] Inline the static-abstract interface-constraint predicate
- Run Repo Assist only on schedule or manual dispatch
- Lenguaje dominante
- F#
- Estrellas
- 4.3k
- Forks
- 879
- Merge medio
- 5 d 12 h
- PR fusionados (30 d)
- 118
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
-
Needs-Triage
Dificultad 1/5 Menos de una hora Aptitud para principiantes 90/100
Los mantenedores suelen responder en 4 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 4 días
-
Bug Needs-Triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Los mantenedores suelen responder en 4 días
-
Needs-Triage vs-insertion
Dificultad 5/5 Más de una semana Aptitud para principiantes 1/100
Los mantenedores suelen responder en 4 días
-
Bug Needs-Triage
Dificultad 4/5 3-5 días Aptitud para principiantes 55/100
dotnet/fsharp#20667 · 1 comentario ·
Los mantenedores suelen responder en 4 días
Todos los issues de dotnet/fsharp
Issues similares
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 90/100
Los mantenedores suelen responder en 1 día
-
area:ci kind:gate-defect
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
InauguralSystems/EigenScript#1448 ·
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
dell/omnia#5425 · 2 comentarios ·
Los mantenedores suelen responder en 1 día
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 85/100
mpfaffenberger/privateer_reimagined#657 ·
Los mantenedores suelen responder en 1 día
-
TS conversion
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
scylladb/nodejs-rs-driver#580 ·
Los mantenedores suelen responder en 2 días