Skip to content

feat: migrate bindings to curried API - #143

Merged
dbrattli merged 11 commits into
mainfrom
feat/curried-string-api
Aug 23, 2026
Merged

feat: migrate bindings to curried API#143
dbrattli merged 11 commits into
mainfrom
feat/curried-string-api

Conversation

@dbrattli

@dbrattli dbrattli commented Aug 22, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • migrate every public OTP and JSX binding module to one curried, pipe-friendly F# surface
  • replace public ImportAll objects in Timer, Io, GenServer, Supervisor, Ets, Logger, and Jsx; retain only internal implementation bindings where appropriate
  • use local module aliases in tests (BString, BGenServer, BEts, etc.) so binding operations stay scoped
  • update README examples and complete the public-module conversion checklist in API-SURFACES.md

Validation

  • dotnet build test/ -m:1
  • Fable to Erlang, rebar3 compilation, and BEAM test run: 412 passed
  • just format-check

just test still encounters its known parallel dotnet build test failure with no diagnostics; the equivalent serial pipeline above passed.

@dbrattli
dbrattli force-pushed the feat/curried-string-api branch from 52b5b7c to 6669c39 Compare August 23, 2026 10:12
@dbrattli dbrattli changed the title feat: unify String bindings on curried API feat: migrate bindings to curried API Aug 23, 2026
@dbrattli
dbrattli marked this pull request as ready for review August 23, 2026 18:24
@dbrattli
dbrattli merged commit dc31680 into main Aug 23, 2026
2 checks passed
@dbrattli
dbrattli deleted the feat/curried-string-api branch August 23, 2026 18:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant