Skip to content

Conversation

@alexcrichton
Copy link
Member

If the dwShareMode parameter is 0 on windows, it "prevents other processes from
opening a file or device if they request delete, read, or write access", which
is the opposite of what we want! This changes the 0 parameter to something which
will allow multiple processes to open the file and then lock it.

If the dwShareMode parameter is 0 on windows, it "prevents other processes from
opening a file or device if they request delete, read, or write access", which
is the opposite of what we want! This changes the 0 parameter to something which
will allow multiple processes to open the file and then lock it.
bors added a commit that referenced this pull request Mar 21, 2014
If the dwShareMode parameter is 0 on windows, it "prevents other processes from
opening a file or device if they request delete, read, or write access", which
is the opposite of what we want! This changes the 0 parameter to something which
will allow multiple processes to open the file and then lock it.
@bors bors closed this Mar 22, 2014
@alexcrichton alexcrichton deleted the fix-rustdoc-windows branch March 22, 2014 04:57
lnicola pushed a commit to lnicola/rust that referenced this pull request Aug 23, 2022
minor: Change tracing event level in apply_change

This is a rather spammy one, it shouldn't be `info`
flip1995 pushed a commit to flip1995/rust that referenced this pull request Jul 11, 2024
Refactor `assigning_clones`

Short list of changes:
* Inline and simplify `extract_call`
* Inline `is_ok_to_suggest`
* Inline `skip_drop_block`
* Check the HIR tree before the macro check
* Don't call `outer_expn_data`
* Use `find` instead of a loop in `clone_source_borrows_from_dest`

changelog: none
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants