What is the purpose of the Generic suffix in this design?

The 'Generic' suffix is used for types that carry a RuntimeToolbox (TB) type parameter, helping developers quickly identify components with runtime dependencies.

Can I use interior mutability in the main body type?

No, this design pattern discourages bringing interior mutability into the body type directly, preferring it to be handled by the shared wrapper layer.

When should I use XyzShared instead of a standard body type?

Use XyzShared when you need multi-thread ownership, need to share the instance across different parts of the application, or must pass it to external components.

How does this skill handle state access within wrappers?

It promotes the use of with_read and with_write methods to access the internal state protected by ToolboxMutex, ensuring safe concurrent access.

Shared Wrapper Design

Name: Shared Wrapper Design
Author: j5ik2o

byj5ik2o

•

개발자 도구

Enforces architectural patterns for shared and non-shared component ownership in Rust concurrent applications.

소개

This skill provides specialized guidance for implementing the Shared Wrapper design pattern in Rust, specifically within the context of concurrent systems using ArcShared and ToolboxMutex. It helps developers make critical design decisions between single-ownership body types and thread-safe shared wrappers, ensuring consistent use of SharedAccess traits and Clone patterns. By following standardized guides for read/write access and naming conventions for generic runtime components, it reduces architectural debt and prevents improper use of interior mutability in complex backend services.

주요 기능

Decision logic for single vs. multi-thread ownership models
Standardized implementation of ArcShared and ToolboxMutex patterns
Naming conventions for Generic runtime components
3 GitHub stars
Guidance on SharedAccess and Clone trait implementations
Transition criteria for moving to complex Handle abstractions

사용 사례

Determining if a new component requires a shared wrapper for multi-threaded safety
Implementing consistent access patterns for shared actors and lookup services
Refactoring internal state management to use thin thread-safe wrappers

소개

주요 기능

Decision logic for single vs. multi-thread ownership models
Standardized implementation of ArcShared and ToolboxMutex patterns
Naming conventions for Generic runtime components
3 GitHub stars
Guidance on SharedAccess and Clone trait implementations
Transition criteria for moving to complex Handle abstractions

사용 사례

Determining if a new component requires a shared wrapper for multi-threaded safety
Implementing consistent access patterns for shared actors and lookup services
Refactoring internal state management to use thin thread-safe wrappers