Check type requirements of Resource and Deleter.

As sometimes N3949 isn't correct or unclear, there should be a list of deviations or implementation decisions.

Instead of testing for execution (executed yes / no) better test for the exact number of executions. As the former may hide multiple calls to the deleter.

Add test coverage.

Implementation of unique_resource (§ 8.4).

As the namespace contains all classes, not just scope guards, it should be changed to something more general. Eg. sr (Scoped Resource, the naming of the Proposal).

Merge headers into scope Header (§ 7.3). It should use a .h extension again.

Check conformance again example Implementation of N3949.

The operator-> requires a type that satisfies (§ 8.4.1/11):

is_pointer<R>::value && (is_class<R>::value || is_union<R>::value)

This however doesn't work, R as either a Pointer type or a class / union.

Implement P0052 (#26) instead of N3949.

• Update project description (, labels, topics, etc.)
• Update documentation
• Implement / update new classes and functions
• Update install targets
• Implement scope Header (#31, #32)

release() Method is noexcept.

Protect the master branch and require successful CI builds.

Factory Functions aren't noexcept.

Implement scope_fail as in § 7.5.2.

scope_exit does no longer need to be move assignable (see § 6.2 No. 3 and 5).

Update

It still has a move ctor and the operators remain deleted. Though the former needs some changes.

N349 has been succeeded: N3949 -> N4189 -> P0052. See here.

The implementation should use this instead.

Implement the copy initialization of LValue ctor overload:

1. Copy the deleter
2. If copying throws:

• Catch exception
• Call the deleter
• Re-throw

Handling Lvalue Reference types, see § 7.5.5/4.

Catch doesn't compile on Clang builds.

This is P0052R5 at the moment.

Add license header to source files.

Even though, it's open for discussion (see § 7.3), it's reasonable and also specified in the current version.

Implement scope_exit as in § 7.5.2.

Maybe it's a good idea to create a branch which uses C++17, as it then can utilize deducing ctors (see § 6.2 No. 4).

Should the header files use Include Guards instead of #pragma once? While the former is standard conform, the latter is much more maintainable and doesn't involve macros.

Handle not no-throw-constructible case of the move ctor.

Implement Unique Resource factory functions as in § 7.5.6.

Implement unique_resource as in § 7.5.5.

Implement release() of scope_guard_t as specified in § 8.3.1/3-4.

Setup Travis CI.

Add installation support through CMake.

Add Testcases for uncaught exception checks of scope_success and scope_fail.

• scope_success
• scope_fail

Use template parameter names as in P0052.

Move-Ctor shall be noexcept.

Should the CI build list the duration of each test case?

Should the type preconditions of Ressrouce and Deleter be checked? Both types shall nothrow move construct / move assign.

Improve call checks in the tests. A mock framework should be used to replace all the annoying and badly maintainable manual work.

No longer required to guard agains throwing deleter (see § 6.2 No. 2).

Move headers to subdirectory to prevent name clashed on file level.

Implement Scope Guard factory functions as in § 7.5.3.

• make_scope_exit()
• make_scope_fail()
• make_scope_success()

Handling for LValue References as described in § 7.5.5/4.

Implement scope_success as in § 7.5.2.

Implement scope Header as described in § 7.5.1.

Classes

• scope_exit – #33
• scope_fail – #34
• scope_success – #35
• unique_resource – #37

Factories

• make_unique_resource_checked() – #39
• make_scope_exit() – #36
• make_scope_fail() – #36
• make_scope_success() – #36
• make_unique_resource() – #39

The std::uncaught_exceptions() is not available in C++14. Both, scope_success (#35) and scope_fail (#34), need it. The only alternative seems std::uncaught_exception() until C++17 is used (#30).

Clarify the return type of release() Method as there are different specifications:

• Specification (§ 8.4 and § 8.4.1): R&&
• Example Implementation (§ 9.2): const R&

Add move-ctor, this is required by #4. The default one can not be used as it's necessary to release the move-from object.

Enhance documentation:

• Compatibility to N3949 / Std
• Installation – #11
• Usage / Examples – Later, when #27 is done, for now see N3949 and tests
• Contribution guide
• Requirements – None, except C++14 and CMake

Improve Catch integration as described here.

Update Catch to latest Dev Build. It then can continue to track upstream again.

Implementation of scope_guard (§ 8.3).