Skip to content

Conversation

@adamsitnik adamsitnik added this to the 6.0.0 milestone Feb 8, 2021
Copy link
Contributor

@carlossanlop carlossanlop left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, pending adding Stephen's suggestion.

@danmoseley
Copy link
Member

I wonder if it would be less confusing if we changed

        internal enum LockType : short
        {
            F_RDLCK = 0,    // shared or read lock
            F_WRLCK = 1,    // exclusive or write lock
            F_UNLCK = 2     // unlock
        }

to

        internal enum LockType : short
        {
            SharedOrReadLock = 0,  
            ExclusiveOrWriteLock = 1,   
            Unlock = 2   
        }

but I don't have a strong opinion.

@adamsitnik
Copy link
Member Author

I wonder if it would be less confusing if we changed

The managed enum is used in only one place in the code and it's unlikely that we are going to reuse it in other places, so I am going to keep it as it is.

@adamsitnik adamsitnik merged commit 2437619 into dotnet:master Feb 15, 2021
@adamsitnik adamsitnik deleted the fileLockingUnix branch February 15, 2021 10:22
@ghost ghost locked as resolved and limited conversation to collaborators Mar 17, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

System.IO.FileSystem tests failing on FreeBSD

4 participants