Skip to content

feat(c): add stable FffResult accessors - #681

Merged
dmtrKovalenko merged 1 commit into
dmtrKovalenko:mainfrom
ciolansteen:feat/stable-result-accessors
Jul 16, 2026
Merged

dmtrKovalenko merged 1 commit into
dmtrKovalenko:mainfrom
ciolansteen:feat/stable-result-accessors

Conversation

@ciolansteen

Copy link
Copy Markdown
Contributor

Summary

  • add stable C accessors for public FffResult payload fields
  • regenerate the public C header
  • cover success, error, pointer, integer, and NULL-result behavior

Motivation

Consumers should not need to depend on the in-memory layout of FffResult. Named accessors make the ABI consumption explicit and let clients such as fff.el avoid raw offsets.

Validation

  • cargo fmt --check -p fff-c
  • cargo test -p fff-c --lib
  • verified exported symbols with nm -D

@dmtrKovalenko
dmtrKovalenko merged commit 57b6773 into dmtrKovalenko:main Jul 16, 2026
52 checks passed
@ciolansteen
ciolansteen deleted the feat/stable-result-accessors branch July 16, 2026 06:07
abhijit-s pushed a commit to abhijit-s/fff that referenced this pull request Jul 17, 2026
Brings in upstream 0.10.0 batch: SDK file-watcher exposure (dmtrKovalenko#674),
stable FffResult C accessors (dmtrKovalenko#681), pi-fff non-cwd + isomorphic
SDK fixes (dmtrKovalenko#622, dmtrKovalenko#669), picker_ui fuzzy-match highlight (dmtrKovalenko#673),
README FAQ (dmtrKovalenko#680), vimdoc regen (dmtrKovalenko#683).

Conflict resolution:
- All crate Cargo.toml + workspace: take ours (0.17.0). Upstream's
  0.10.0 is its own independent release line; the fork stays on 0.17.0.
  fff-mcp keeps its daemon-only deps (fff-ipc/dirs/libc).
- fff-core/src/lib.rs: keep BOTH the fork's content_staleness_recheck
  test module and upstream's new pub watch module (non-overlapping).
- install-mcp.sh: keep ours — the fork installs from HEAD/source and
  points at abhijit-s, so upstream's v0.10.0 release-pinning + SHAs
  do not apply.
- Cargo.lock: ours (no reconciliation needed on build).

Verified: build-daemon green; fff-search suite incl. upstream's new
watch:: tests + the fork's 4 content_staleness_recheck regressions;
daemon crate tests — all 0 failures.
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.

2 participants