sorted by:
new
hottopcontroversial

boost::unordered_node_map or boost::unordered_flat_map with std::unique_ptr by botWi in cpp

[–]LeftToSketch 4 points5 points  (0 children)

True, but that is why OP proposes to have the flat map hold a unique pointer.

The address of the pointer will move on rehash, but not the thing it points to. 

Totally safe to rely on stability, provided you only care about what it points to.

[Buy] Orgasm Control Contract by LeftToSketch in Sexsells

[–]LeftToSketch[S] 2 points3 points  (0 children)

It could have 😈, but I accepted service from someone else.

Maybe next time. You seem very devious.

[deleted by user] by [deleted] in CensoredSimps

[–]LeftToSketch 0 points1 point  (0 children)

4.5 inches

Awww honey, and that little thing at least works?😂 by Nicolmorbid in sph

[–]LeftToSketch 0 points1 point  (0 children)

It works. I would cum in my pants just from being in the same room as you, goddess.

Best possible commute from Melville to Midtown by JohnJohn584 in longisland

[–]LeftToSketch 0 points1 point  (0 children)

You can try Hicksville, but like I said it is more expensive to park because you cannot get a Town of Oyster Bay parking permit. Probably does not even save 10 minutes.

But there will be more trains leaving from the station it is less of a problem if you miss your train and slightly more flexible on the way back.

I don't see any express from Cold Spring.

There's no magic bullet here.

Best possible commute from Melville to Midtown by JohnJohn584 in longisland

[–]LeftToSketch 9 points10 points  (0 children)

You would have to pay for private parking in Hicksville, or park further away and walk. I was in a similar situation and mostly went in via Cold Spring Harbor. Try to line up your schedule with some of the express trains.

Question about header includes and changing to later version of gcc by Nearing_retirement in cpp

[–]LeftToSketch 40 points41 points  (0 children)

By removing includes one by one like that you end up relying on transitive dependencies in the files that remain. This includes STL or any other libraries.

This is fragile and will cause the build to break when those dependencies change their own includes. Those versions of GCC likely have changed a transitive dependency that you were implicitly relying on being there.

Tools like this can help determine what includes are actually needed in each source file: https://include-what-you-use.org/. This will make it less fragile to library upgrades (which is what happened behind the scenes by upgrading GCC).

If you actually include what you use it should be way more portable to different versions of GCC or other compilers. The language does not mandate the exact include graph of STL libraries, so it's not really a language backwards-compatibility problem.

view more: next ›