Skip to content

Cannot override DirectoryIterator::current() without return typehint in 8.1 #8192

Closed

Description

@zerocrates

Description

The following code:

<?php
class OverrideValidDirectoryIterator extends DirectoryIterator {
    public function valid() {
        return null;
    }
}

class OverrideCurrentDirectoryIterator extends DirectoryIterator {
    public function current() {
        return null;
    }
}

Resulted in this output:

Deprecated: Return type of OverrideValidDirectoryIterator::valid() should either be compatible with DirectoryIterator::valid(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /in/S7tkM on line 4

Fatal error: Declaration of OverrideCurrentDirectoryIterator::current() must be compatible with DirectoryIterator::current(): mixed in /in/S7tkM on line 10

Obviously the first here is just a form of the documented 8.1 deprecation of overriding core classes without matching return typehints, but unlike for other methods on DirectoryIterator, overriding current() in this way is a fatal error and not an E_DEPRECATED, and the ReturnTypeWillChange attribute has no effect.

PHP Version

PHP 8.1.3

Operating System

No response

Activity

  1. changed the title [-]Cannot override DirectoryIterator::current() in 8.1[/-] [+]Cannot override DirectoryIterator::current() without return typehint in 8.1[/+] on Mar 11, 2022
  2. iluuu1994 commented on Mar 11, 2022

    @iluuu1994
    Member

    I haven't actually checked but I think that might come down to no return type meaning mixed|void. Since mixed|void is not a subtype of mixed but the other way around, omitting the type here would make the signature incompatible. Although since in PHP void still returns null that doesn't really matter. So allowing this, at least for internal methods, could still make sense.

    Edit: But yes you're right in either case this should at most emit a deprecation.

  3. zerocrates commented on Mar 12, 2022

    @zerocrates
    Author

    Yeah, I'm not reporting about the incompatibility of mixed and "no hint", but just that in this case it's an error where the documentation indicates it should be a deprecation, as you said in your edit.

  4. added a commit that references this issue on Mar 12, 2022
    d0a0518
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions