Björn Fahller

You have not shown what `A` looks like above, so it's not obvious what's happening, but it looks to me like you're expecting the library to work outside the rules...

The answer is that it honestly never occurred to me that this would be a use case. Why do you want to have a const underlying type? I think the...

The problem with `strong::type` is that it can't be move constructed. With your example it probably doesn't matter, but in general it's problematic. Maybe you should write your own type,...

Would this work? https://godbolt.org/z/n9853n3ex I'd have to figure out a way to make `value_of()` only return `const&` for immutable types.

Try branch [immutable](https://github.com/rollbear/strong_type/tree/immutable) and tell me if it's OK for your use case. You use it with a non-const underlying type, and a `strong::immutable` modifier.

Wow. I had no idea that this was even allowed. Can you please show an example of a coroutine that behaves this way? I have some learning to do.

There is no "correct" approach. It depends. I've chosen to not implement it because I don't know how to make a good policy handler that is generic and will always...

Sorry, for some reason I completely missed that you added things here. You may want to have a look at branch [immutable](https://github.com/rollbear/strong_type/tree/immutable), where a new modifier `strong::immutable` is added. I...