Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

Issues from a bug hunt over master (eb087382 to cd641cbc)

Geschlossen
  • Stimmt etwas nicht?
#9,109 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
15/100
Issue-Typ
Bug
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
javascript
Bereich
compilers

Rechercherichtung

Start with the linked issues #9098–#9108, which describe the individual findings, and review the commit range from eb087382 to cd641cbc that the hunt examined. The parent issue groups 22 findings across compiler behavior, tooling, parsing, and formatting, so choose a specific linked issue before investigating. Done means reproducing and fixing that issue’s reported behavior.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

Found by a bug hunt over the 16 commits from eb087382 to cd641cbc (26–27 October 2026).

The hunt started from the changes in those commits, looked for regressions, and reported older bugs it ran into along the way. Every finding was reproduced on a build of cd641cbc, checked again by an independent pass, and compiled at b123b7c3 to tell regressions apart from older bugs. Existing issues were searched first, and related ones are linked from each issue.

In numbers: 11 issues covering 22 findings. Three more suspected problems turned out not to be bugs and are not filed. 5 are regressions in this range: the untagged Date case in the first issue, both line-ending problems, the failwith placeholder, and the per-module copyWithin type.

Wrong code or wrong values

  • #9098 x !== true && x !== false is simplified to false when x is not a boolean (regression for one shape)
  • #9099 Float constants never compare equal in the JS simplifier: x == 2.5 && x == 2.5 compiles to false
  • #9100 bsc -format changes string literals that contain line breaks, and is not idempotent on \r\r\n (regression)
  • #9101 Formatter moves an attribute in front of ~a as x: int onto x
  • #9103 TypedArray: copyWithin/copyAllWithin are typed as returning array, and TypedArray.map can change the element type
  • #9104 JSX: plain and preserve mode evaluate children and props in different orders

Tooling and diagnostics

  • #9102 Editor code actions generate failwith("TODO"), which no longer exists (regression)
  • #9105 Coercion hint: suggestion that doesn't compile after a parenthesized operand, and the hint names the expanded type

Parser and printer

  • #9106 Parser rejects private @attr {…} and a doc comment before a non-record type
  • #9107 Formatter: five cases where comments and doc comments are placed wrongly
  • #9108 Lexer rejects a UTF-8 BOM, and a lone \r does not end a line

🤖 Generated with Claude Code

Vorherrschende Sprache
OCaml
Sterne
7.5k
Forks
484
Ø Merge
20 Std. 43 Min.
Gemergte PRs (30 T.)
263

Entwicklungsumgebung

In Codespaces öffnen

Startet den Dev-Container des Projekts im Browser, mit Ihrem eigenen GitHub-Konto.

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus rescript-lang/rescript

Alle Issues in rescript-lang/rescript

Ähnliche Issues

Weitere Issues zu Compilers

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.