Arvid Norberg

I think the most obvious example is for enums. ``static_cast`` is what you use to get the underlying integer value. I would argue that the fact that the language provides...

@viboes Yes, once I actually started working on it, with the intention to patch boost.endian, it turned out to be much simpler to build a new primitive on top of...

I take you specifically refer to the case of traditional code taking a parameter by non-const reference, as an out-parameter. If it's just a matter of casting the result of...

I see. In my mind, that should be typed as: ``` x = MyInt{f()}; ``` But you won't really get all the type-safety benefits until ``f()`` returns ``MyInt``.

my opinion is that along the edges of introducing strong types, it's a feature for the conversions to be verbose and explicit. The two cases I can think of is...

in `file::close` (file.cpp in RC_1_0 branch) there is a condition like this:: ``` if ((rw_mode != read_only) && (m_open_mode & sparse) && !is_sparse(m_file_handle, use_overlapped)) ``` It is expected that when...

> libtorrent seems to switch from using mmap to using read/write when it detects that there's a network filesystem, however this doesn't fix all of the performance issues with it....

right, there's a special case for small files. They are read and written using regular `read()` and `write()` calls.

it's primarily that the attack surface of libtorrent is significantly larger with webtorrents enabled. It's especially disappointing to be hacked by a feature you're not using.

surely any client that wants to support webtorrents would enable it. Why is the default so significant?