Struct File

vfs/file.go:42–62

The File object is tightly coupled to the Dir object. Since they both have locks there is plenty of potential for deadlocks. In order to mitigate this, we use the following conventions File may **only** call these methods from Dir with the File lock held. Dir.Fs Dir.VFS (As these are read only an

// File represents a file or a symlink
type File struct {
	inode uint64          // inode number - read only
	size  atomic.Int64    // size of file
	ctx   context.Context // context for VFS operations - read only

	muRW sync.Mutex // synchronize RWFileHandle.openPending(), RWFileHandle.close() and File.Remove

	mu               sync.RWMutex                    // protects the following
	d                *Dir                            // parent directory
	dPath            string                          // path of parent directory. NB dir rename means all Files are flushed
	o                fs.Object                       // NB o may be nil if file is being written
	leaf             string                          // leaf name of the object
	writers          []Handle                        // writers for this file
	virtualModTime   *time.Time                      // modtime for backends with Precision == fs.ModTimeNotSupported
	pendingModTime   time.Time                       // will be applied once o becomes available, i.e. after file was written
	pendingRenameFun func(ctx context.Context) error // will be run/renamed after all writers close
	sys              atomic.Value                    // user defined info to be attached here
	nwriters         atomic.Int32                    // len(writers)
	appendMode       bool                            // file was opened with O_APPEND
	isLink           bool                            // file represents a symlink
}

// newFile creates a new File
//