Give more information on thread-abort safe #7362
Conversation
|
Docs Build status updates of commit fa269b9: ✅ Validation status: passed
For more details, please refer to the build report. Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report. For any questions, please:
|
|
Docs Build status updates of commit 477bc8c: ✅ Validation status: passed
For more details, please refer to the build report. Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report. For any questions, please:
|
Co-authored-by: Eric Erhardt <eric.erhardt@microsoft.com>
|
Docs Build status updates of commit 47f6c44: ✅ Validation status: passed
For more details, please refer to the build report. Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report. For any questions, please:
|
Summary
I was thinking about using ReaderWriterLockSlim, later I was scared of using it because the caution said it is not thread-abort safe, I decided not to use it. After hours of searching, reading, and doing an experiment, I found out the .NET Core environment, which I was working on, does not have thread abort anymore.
I would like to give more information on thread-abort safe, it helps people with less experience might not get into my problem.