Improve ffi::specialize_for macro and add new ffi::specialize macro #33
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR implements improvements to the FFI specialization macros as requested in issue #11. The improvements focus on reducing verbosity and providing better developer experience while maintaining backward compatibility.
✨ Key Changes
conventionparameter optional inffi::specialize_for- defaults to C# conventionffi::specializemacro for embedded annotations with sensible defaultsbox_syntaxfeature🔄 Before and After
Before (Verbose):
After (Option 1 - Simplified):
After (Option 2 - Embedded Annotations):
#[ffi::specialize("doublets_constants_*")]🧪 Test Plan
📁 Files Changed
doublets-ffi/ffi-attributes/src/lib.rs- Core implementationexamples/ffi_test.rs- Working examplesexamples/usage_examples.md- Documentation🎯 Implementation Details
Implemented both approaches suggested in the issue:
ffi::specialize_forwith optional convention (implemented)ffi::specializemacro for embedded annotations (implemented)Both generate identical FFI functions with C# naming conventions for
u8,u16,u32,u64types.Fixes #11
🤖 Generated with Claude Code