fn opendir(
        &self,
        ctx: Context,
        inode: Self::Inode,
        flags: u32,
    ) -> io::Result<(Option<Self::Handle>, OpenOptions)> {
        // Matches the behavior of libfuse.
        Ok((None, OpenOptions::empty()))
    }
/// Open a directory for reading.
///
/// The file system may choose to return a `Handle` to refer to the newly opened directory. The
/// kernel will then use this `Handle` for all operations on the content of the directory
/// (`readdir`, `readdirplus`, `fsyncdir`, `releasedir`). If the file system does not return a
/// `Handle` then the kernel will use the `Inode` for the directory to operate on its contents.
/// In this case the file system may wish to enable the `FsOptions::ZERO_MESSAGE_OPENDIR`
/// feature if it is supported by the kernel (see below).
///
/// The returned `OpenOptions` allow the file system to change the way the opened directory is
/// handled by the kernel. See the documentation of `OpenOptions` for more information.
///
/// If the `FsOptions::ZERO_MESSAGE_OPENDIR` feature is enabled by both the file system
/// implementation and the kernel, then the file system may return an error of `ENOSYS`. This
/// will be interpreted by the kernel as success and future calls to `opendir` and `releasedir`
/// will be handled by the kernel without being passed on to the file system.
Open a directory for reading.
The file system may choose to return a `Handle` to refer to the newly opened directory.

The returned `OpenOptions` allow the file system to change the way the opened directory is
handled by the kernel. See the documentation of `OpenOptions` for more information.

If the `FsOptions::ZERO_MESSAGE_OPENDIR` feature is enabled by both the file system
implementation and the kernel, then the file system may return an error of `ENOSYS`. This
will be interpreted by the kernel as success and future calls to `opendir` and `releasedir`
will be handled by the kernel without being passed on to the file system.
Open a directory for reading . The file system may choose to return a ` Handle ` to refer to the newly opened directory . The returned ` OpenOptions ` allow the file system to change the way the opened directory is handled by the kernel . See the documentation of ` OpenOptions ` for more information . If the ` FsOptions :: ZERO_MESSAGE_OPENDIR ` feature is enabled by both the file system implementation and the kernel then the file system may return an error of ` ENOSYS ` . This will be interpreted by the kernel as success and future calls to ` opendir ` and ` releasedir ` will be handled by the kernel without being passed on to the file system .
fn opendir(
        &self,
        ctx: Context,
        inode: Self::Inode,
        flags: u32,
    ) -> io::Result<(Option<Self::Handle>, OpenOptions)> {
        // Matches the behavior of libfuse.
        Ok((None, OpenOptions::empty()))
    }
fn opendir ( & self , ctx : Context , inode : Self :: Inode , flags : u32 , ) -> io :: Result < ( Option < Self :: Handle > , OpenOptions ) > { // Matches the behavior of libfuse. Ok ( ( None , OpenOptions :: empty ( ) ) ) }
Open a directory for reading.
Open a directory for reading .
&self
ctx
Context
inode
Self::Inode
flags
u32