LouisCharlesC

- First part, naming: `safe::lock_guard` does not seem right because you need a way to specify whether it is a read-only or a read-write access. In similar libraries, I remember...

I like it. Unfortunately, my eyes see `safe::read::LockGuard(foo)`. Stupid CamelCase glasses...

Not sure the extra param cuts it. Today, read-only Access and read-write Access are separate classes. The `safe::lock_guard(foo, safe::read_access)` you suggest could be a factory that returns the right object....

Hey, I don't know enough about copyrights to even know if I answer your question. Please tell me if I somehow miss the point or need to give you more...

> So InstallTarget.cmake is just based on the talk, but not copied from there, right? I'll have to ask what exactly is meant by "copying" ? Do I have to...

Phew, good! Out of curiosity, can I ask why you are doing this? I'm not even sure I know what "packaging for debian" really means! Thanks.

Cool, thanks for doing this :) Shall we close this issue ?

After a bit more thinking, it seems that: - The invocables would not be called immediately, but at connection. - Of course I can't just pass a pack of senders...

Dear Lord, the readme was wrong. I just fixed it, thanks! Now for the other problem, the code in the accessmode.h file lives in the namespace `safe`, so it does...

Readme fixed again, thanks again! Ok, well the code example does do it. It's just that since it is enclosed by `namespace safe {}` then the `safe::` is not necessary....