Named Implicits Wrappers Feature

[zienag]

Overview

Add support for named implicits wrappers - closure factories that capture implicit dependencies at definition time and provide them when invoked later.

Usage Pattern

// Define wrapper usage
withFooImplicits { scope in
    requires(scope)
}

// With additional parameters
withFooImplicits { (arg1: Int, arg2: String, scope) in
    // use arg1, arg2, and implicits via scope
}

Implementation Tasks

• Basic wrappers (synchronous, non-throwing)
• Async/throws support (auto-detect from closure body)
• #withImplicits macro for anonymous wrappers
• Documentation

[zienag]

Progress Update

Completed

• Basic wrappers — PR Add named implicits wrappers (withFooImplicits pattern) #6
  • Synchronous, non-throwing wrapper generation
  • Support for 0 to N additional closure parameters

In Progress

• Async/throws support
  • PR Add effect detection for closures (isAsync/isThrowing) #17 added effect detection infrastructure (isAsync/isThrowing on ClosureExpr)
  • Remaining: pass effect info through pipeline and generate async/throwing wrapper variants

Not Started

• #withImplicits macro
• Documentation