Leaks configuration

[Therzok]

Any reason for having this?

[nulltoken]

See SafeHandleBase.

A warning is issued when we forgot to explicitly release a handle. The configuration allows to activate the StackTrace and find out where the handle was initially "allocated".

[Therzok]

Well, can't we just define a LEAKS symbol in Debug/Release whenever we want to? I see no need for an extra configuration.

[nulltoken]

👍

Would you fancy a PR? 😉

[Therzok]

Sir, will do, sir!

[Therzok]

Here's the deal: I'll make a PR which fixes 3 issues or 3 PRs which fix these issues in the following order:

• Make the Linux/MacOSX experience slightly more delightful #837
• Leaks configuration #869 - Possibly document in CONTRIBUTING ?
• Create a CONTRIBUTING.md file #847

[nulltoken]

I think having 3 separated PRs would be easier. Some would be easier to merge/less subject to debate than others. Also, one PRs may turn into a hell of fixups for you.

I'd go with 3. Feel free to transmute the issues into PRs. I tend to do this though http://issue2pr.herokuapp.com/.