borrowscope-macro: Rust's Type Information Barrier

Table of Contents

• 1. Introduction
• ▶ 2. Background: The BorrowScope Project
  • 2.1 Project Overview
  • 2.2 The Role of borrowscope-macro
  • 2.3 The Instrumentation Gap
• ▶ 3. Understanding Rust's Compilation Pipeline
  • 3.1 The Compilation Phases
  • 3.2 What Procedural Macros Receive
  • 3.3 When Type Information Becomes Available
• ▶ 4. The Type Information Barrier
  • 4.1 The Fundamental Constraint
  • 4.2 Why This Design Exists
  • 4.3 The syn Crate: Powerful but Syntactic
• ▶ 5. Concrete Manifestations of the Problem
  • 5.1 FFI Function Detection
  • 5.2 Union Field Access
  • 5.3 Static Variable Access
  • 5.4 Type-Dependent Method Behavior
  • 5.5 Summary: The Pattern
• ▶ 6. Architectural Solutions
  • 6.1 Custom Rustc Driver
  • 6.2 Two-Phase Architecture
  • 6.3 rust-analyzer Integration
  • 6.4 External Type Query Tool (RTK)
  • 6.5 Annotation-Based Disambiguation
  • 6.6 Enhanced Heuristics
• ▶ 7. Comparative Analysis
  • 7.1 Evaluation Criteria
  • 7.2 Solution Comparison Matrix
  • 7.3 The Nightly Question
  • 7.4 The 95% Argument
• ▶ 8. Recommended Approach for BorrowScope
  • 8.1 Phased Implementation Strategy
  • 8.2 Phase 1: Annotation System Design
  • 8.3 Phase 2: Validation Tool Architecture
  • 8.4 Phase 3: Full Compiler Integration
• ▶ 9. Conclusion
  • 9.1 Key Takeaways
  • 9.2 Broader Implications
  • 9.3 Call to Action
• 10. References
• Appendix A: Glossary