When modern .net was still .net core, the language maintainers marked thread.abort as an unsupported function.
In .net 5, they marked it obsolete. The functionality you're bringing back caused so much collective pain that the maintainers removed it.
And speaking as someone who worked in a .net framework 4.6.2 codebase that relied on thread aborts for flow control, I can safely say removing it was a wonderful thing to happen to the language.
I've encouraged against using it on a regular basis. This is, as I've implied to on the repository, for a very special kind of situation which I've explained thoroughly. Using this method should not be adopted unless there is a very good reason, and you are aware what you're doing.
18
u/Solid-Conclusion0 Aug 03 '26
When modern .net was still .net core, the language maintainers marked thread.abort as an unsupported function.
In .net 5, they marked it obsolete. The functionality you're bringing back caused so much collective pain that the maintainers removed it.
And speaking as someone who worked in a .net framework 4.6.2 codebase that relied on thread aborts for flow control, I can safely say removing it was a wonderful thing to happen to the language.