Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Issues from differential semantic drift analysis (a7721303 to b123b7c3)

Chiusa
#8,980 0 commenti 0 reazioni 1 assegnatario Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@cknitt ci sta già lavorando.

Dal 23/10/2026.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

Found by differential semantic drift analysis from a7721303 to b123b7c3.

These are the results of semantic drift analysis of the 119 commits merged since the previous round (#8768). The analysis covered the new language representations and every consumer that matches on them, the leftovers of removals and refactors, the OCaml and Rust build systems side by side, and the changelog, semantic diff and CI tooling. Each finding was checked by a second, independent pass against master and against existing issues and pull requests; none repeats an item of #8712 or #8768. Every issue states what is broken and where, and a separately labelled speculation on the cause.

In numbers: 11 issues covering 23 findings: 2 behaviour bugs and 1 test that hides failures (3 issues), 10 inconsistencies between docs, diagnostics, schema, changelog or tools and the code (6 issues), 3 pieces of duplicated logic (1 issue) and 7 dead or stale items (1 issue). Of the ten issues from the previous round, #8770 fixed nine; #8762 was closed deliberately.

Behaviour

  • #8974 let delete and let $$delete produce a duplicate ES export and an overwritten CommonJS export
  • #8975 genType emits char as a TypeScript type
  • #8979 concurrent_async_context reports a cleanup error instead of the compile failure and leaks its temp dir

Inconsistencies

  • #8969 make test-rewatch is documented as the Rust build system's test command but tests the OCaml one
  • #8970 Build schema says namespace-entry without a namespace has no effect; rescript rejects it
  • #8971 Unreleased changelog fragments that no longer describe the release
  • #8972 yarn test-commit-records is not run in CI
  • #8973 The @as error message omits float and bigint, which @as accepts
  • #8978 Doc-comment attributes: editor analysis accepts @ocaml.doc/@ns.doc, genType and the printer do not

Duplication and dead code

  • #8976 Logic maintained in several copies: load-path lookup, identifier classifier, ident hash sets
  • #8977 Dead code, stale comments and unused test inputs left by recent changes

🤖 Generated with Claude Code

Lingua principale
OCaml
Stelle
7.5k
Fork
483
Merge medio
20h 7m
PR unite (30g)
227

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di rescript-lang/rescript

Tutte le issue di rescript-lang/rescript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.