168 lines
3.8 KiB
Markdown
168 lines
3.8 KiB
Markdown
|
# Reflection System Implementation Plan
|
||
|
|
|
||
|
|
## Core Design
|
||
|
|
Following the Dart mirrors API design while maintaining cross-platform compatibility.
|
||
|
|
|
||
|
|
### Mirror System
|
||
|
|
```dart
|
||
|
|
abstract class MirrorSystem {
|
||
|
|
Map<Uri, LibraryMirror> get libraries;
|
||
|
|
LibraryMirror findLibrary(Symbol libraryName);
|
||
|
|
IsolateMirror get isolate;
|
||
|
|
TypeMirror get dynamicType;
|
||
|
|
TypeMirror get voidType;
|
||
|
|
TypeMirror get neverType;
|
||
|
|
}
|
||
|
|
```
|
||
|
|
|
||
|
|
### Core Mirrors
|
||
|
|
```dart
|
||
|
|
abstract class Mirror {}
|
||
|
|
|
||
|
|
abstract class DeclarationMirror implements Mirror {
|
||
|
|
Symbol get simpleName;
|
||
|
|
Symbol get qualifiedName;
|
||
|
|
DeclarationMirror? get owner;
|
||
|
|
bool get isPrivate;
|
||
|
|
bool get isTopLevel;
|
||
|
|
List<InstanceMirror> get metadata;
|
||
|
|
}
|
||
|
|
|
||
|
|
abstract class ObjectMirror implements Mirror {
|
||
|
|
InstanceMirror invoke(Symbol memberName, List positionalArgs, [Map<Symbol, dynamic> namedArgs]);
|
||
|
|
InstanceMirror getField(Symbol fieldName);
|
||
|
|
InstanceMirror setField(Symbol fieldName, Object? value);
|
||
|
|
}
|
||
|
|
```
|
||
|
|
|
||
|
|
### Type System
|
||
|
|
```dart
|
||
|
|
abstract class TypeMirror implements DeclarationMirror {
|
||
|
|
bool get hasReflectedType;
|
||
|
|
Type get reflectedType;
|
||
|
|
List<TypeVariableMirror> get typeVariables;
|
||
|
|
List<TypeMirror> get typeArguments;
|
||
|
|
bool get isOriginalDeclaration;
|
||
|
|
TypeMirror get originalDeclaration;
|
||
|
|
bool isSubtypeOf(TypeMirror other);
|
||
|
|
bool isAssignableTo(TypeMirror other);
|
||
|
|
}
|
||
|
|
```
|
||
|
|
|
||
|
|
## Implementation Phases
|
||
|
|
|
||
|
|
### Phase 1: Core Mirror System
|
||
|
|
1. Basic Mirror interfaces
|
||
|
|
- Mirror base class
|
||
|
|
- DeclarationMirror
|
||
|
|
- ObjectMirror
|
||
|
|
- TypeMirror
|
||
|
|
|
||
|
|
2. Instance Reflection
|
||
|
|
- InstanceMirror implementation
|
||
|
|
- Method invocation
|
||
|
|
- Field access
|
||
|
|
- Constructor invocation
|
||
|
|
|
||
|
|
3. Type Reflection
|
||
|
|
- ClassMirror implementation
|
||
|
|
- Type information handling
|
||
|
|
- Member reflection
|
||
|
|
- Metadata support
|
||
|
|
|
||
|
|
### Phase 2: Type System
|
||
|
|
1. Type Mirrors
|
||
|
|
- TypeMirror implementation
|
||
|
|
- TypeVariableMirror
|
||
|
|
- Generic type support
|
||
|
|
- Type relationships
|
||
|
|
|
||
|
|
2. Method Reflection
|
||
|
|
- MethodMirror implementation
|
||
|
|
- Parameter handling
|
||
|
|
- Return type resolution
|
||
|
|
- Invocation support
|
||
|
|
|
||
|
|
3. Field Reflection
|
||
|
|
- VariableMirror implementation
|
||
|
|
- Property access
|
||
|
|
- Field metadata
|
||
|
|
- Type checking
|
||
|
|
|
||
|
|
### Phase 3: Advanced Features
|
||
|
|
1. Library Support
|
||
|
|
- LibraryMirror implementation
|
||
|
|
- Symbol resolution
|
||
|
|
- Privacy handling
|
||
|
|
- Library dependencies
|
||
|
|
|
||
|
|
2. Metadata System
|
||
|
|
- Annotation support
|
||
|
|
- Metadata reflection
|
||
|
|
- Declaration scanning
|
||
|
|
- Attribute handling
|
||
|
|
|
||
|
|
### Phase 4: Platform Support
|
||
|
|
1. Web Platform
|
||
|
|
- Tree shaking support
|
||
|
|
- Minification handling
|
||
|
|
- Browser optimizations
|
||
|
|
- JS interop
|
||
|
|
|
||
|
|
2. Native Platforms
|
||
|
|
- AOT compilation support
|
||
|
|
- Native optimizations
|
||
|
|
- Memory management
|
||
|
|
- Performance tuning
|
||
|
|
|
||
|
|
## Testing Strategy
|
||
|
|
|
||
|
|
### Unit Tests
|
||
|
|
1. Core Functionality
|
||
|
|
- Mirror creation
|
||
|
|
- Type reflection
|
||
|
|
- Member access
|
||
|
|
- Method invocation
|
||
|
|
|
||
|
|
2. Type System
|
||
|
|
- Type relationships
|
||
|
|
- Generic handling
|
||
|
|
- Type variables
|
||
|
|
- Type metadata
|
||
|
|
|
||
|
|
### Integration Tests
|
||
|
|
1. System Tests
|
||
|
|
- Full reflection scenarios
|
||
|
|
- Cross-platform behavior
|
||
|
|
- Edge cases
|
||
|
|
- Error handling
|
||
|
|
|
||
|
|
2. Performance Tests
|
||
|
|
- Memory usage
|
||
|
|
- Operation speed
|
||
|
|
- Resource management
|
||
|
|
- Platform behavior
|
||
|
|
|
||
|
|
## Success Criteria
|
||
|
|
|
||
|
|
### Functional
|
||
|
|
- Complete mirrors API implementation
|
||
|
|
- Cross-platform compatibility
|
||
|
|
- Full type system support
|
||
|
|
- Metadata handling
|
||
|
|
|
||
|
|
### Technical
|
||
|
|
- Matches Dart mirrors behavior
|
||
|
|
- Efficient memory usage
|
||
|
|
- Fast reflection operations
|
||
|
|
- Platform optimizations
|
||
|
|
|
||
|
|
## Timeline
|
||
|
|
- Phase 1: 3 weeks
|
||
|
|
- Phase 2: 3 weeks
|
||
|
|
- Phase 3: 2 weeks
|
||
|
|
- Phase 4: 2 weeks
|
||
|
|
- Total: 10 weeks
|
||
|
|
|
||
|
|
This plan focuses on implementing the core Dart mirrors API while ensuring cross-platform compatibility and performance. By following the established mirrors API, we ensure our reflection system will be familiar to Dart developers and capable of supporting any use case that the original mirrors system supports.
|