You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Compatibility is being tracked in compatibility.md. We need to aim for all features it is possible to implement. Unfortunately we cannot implement "all" the functionality, for example:
Extension-related things ReflectionExtension - I don't think we have a way to access the information required by this, nor to tie it all up with our userland reflection (I may be wrong?) - see Implement extensions reflection #15
Methods ReflectionMethod->invoke as we are not actually loading the classes, we cannot really invoke methods (yes, it's technically possible, but not logical) - see Implement accessors without instantiating #14
State modifications like ReflectionProperty->setAccessible and ReflectionProperty->setValue these require instances of classes, but we never instantiate classes - see Implement accessors without instantiating #14
Instance-requiring ReflectionObject simply because it requires an instance, we cannot implement it, because that would require the class to be loaded - see Implement ReflectionObject #16
Compatibility is being tracked in compatibility.md. We need to aim for all features it is possible to implement. Unfortunately we cannot implement "all" the functionality, for example:
ReflectionExtension
- I don't think we have a way to access the information required by this, nor to tie it all up with our userland reflection (I may be wrong?) - see Implement extensions reflection #15ReflectionMethod->invoke
as we are not actually loading the classes, we cannot really invoke methods (yes, it's technically possible, but not logical) - see Implement accessors without instantiating #14ReflectionProperty->setAccessible
andReflectionProperty->setValue
these require instances of classes, but we never instantiate classes - see Implement accessors without instantiating #14ReflectionObject
simply because it requires an instance, we cannot implement it, because that would require the class to be loaded - see Implement ReflectionObject #16ReflectionFunctionAbstract->isClosure
can't be implemented currently - see Add ability to create a ReflectionFunction from a closure #37Compatibility summary
The text was updated successfully, but these errors were encountered: