I tried searching before posting, but didn't find an answer... kind of hard to word something like this in a search. (Edit to clarify before someone suggests throwing everything in bags-- Yes, I can use ziplocs/silicone equivalents to ziplocs, but I need pans of stuff I can just throw in the oven too)
This guide was written as an appendix to the std::hive (nee: colony) standards proposal - but mainly for my own amusement. If anyone has any critique or questions, please comment! Otherwise, hope it helps someone. I realise the exact format I've given is not absolutely perfect, but I tried a few layouts and it was the best.
Note, this guide does not cover:
- All known C++ containers
- Multithreaded usage/access patterns in any depth
- All scenarios
- The vast variety of map variants and their use-cases
- Examinations of technical nuance (eg. at which sizeof threadhold on a given processor does a type qualify as large enough to consider not using it in a vector if there is non-back erasure?). For that reason I'm not going to qualify 'Very large' or 'large' descriptors in this guide.
These are broad strokes and can be treated as such. Specific situations with specific processors and specific access patterns may yield different results.There may be bugs or missing information. The strong insistence on arrays/vectors where-possible is to do with code simplicity, ease of debugging, and performance via cache locality. The relevance of all assumptions is subject to architecture.The benchmarks this guide is based upon are available here and here.
Start!
a = yes, b = no
- Is all you're doing just inserting to the back of the container and iterating?
0a. Do you know the largest possible maximum capacity you will ever have for this container, and is the lowest possible maximum capacity not too far away from that?
0aa. If so, use an array.
0ab. if not, use a vector.
0b. Can you change your data layout or your processing strategy so that back insertion and iterating would be all you're doing?
0ba. If so, do that and goto 0a.
0bb. If not, Goto 1.
0b. Goto 1.
- Is the use of the container stack-like, queue-like or ring-like?
1a. If stack-like, use plf::stack, if queue-like, use plf::queue (both are faster than the std:: equivalent adaptors, have stable pointers to elements and are configurable in terms of memory block sizes). If ring-like, use "ring_span lite".
1b. If not, goto 2.
- Does each element need to be accessible via an identifier ie. key? ie. is the data associative.
2a. If so, is the number of elements small and the type sizeof not large?
2aa. If so, is the value of an element also the key?
2aaa. If so, just make an arr
... keep reading on reddit ➡Hi all,
In our environment, we deploy a Debian application to client-facing terminals. That said, we and our devs are using EL-based laptops to do work.
Occasionally, we have to run the application (which normally runs on Debian 8-10) on our laptops. The current solution is a hack at best. I know we can do this better.
I've quickly read about Flatpak, Snap, and Appimage. I'm not positive any of these solve the problem. I effectively want a minimal Debian 10 runtime in a container and then I can layer the application on top. We have over 20 environments for the application, so I need over 20 of these different containers.
I've used Podman/Docker before, but only for server applications. It kinda sounds like it need Podman/Docker but for my desktop application.
Cheers
Trying to be zero waste but I can't tell if using cows milk in reuseable bottles I can bring back is worse than plant milks in plastic packing (tetrapacks, big plastic jugs). I' am trying to put a bit more thought into my strategies to help minimize carbon emissions as well as zero waste but I can't find zero waste plant milks very easily that are not a million dollars.
I also cannot make my own as I could not, with all the different recipes I tried, make good oatmilk. I also read that nut milks, which I could make, are also not great environmentally so I should stay away from those aw well.
So stuck in between a rock and a hard place and would appreciate any thoughts on the matter :)
I'm looking for a tool like Container Nursery but then for Proxmox LXC containers instead of Docker containers.
My server makes a lot of noise, even when services are not being accessed. By only enabling containers when needed I will be able to reduce noise and energy consumption.
Do TurnKey LXC containers support wake on lan functionality? Some information was found in this blogpost.
Chapter 5 of ug994 is all about "Modular Design with Block Design Containers" but from what I can tell you can only use bottom up flow if you save BDs as .bd design sources rather than as TCL scripts (🤮).
Top down flow doesn't seem any better since I have to pre-make all the sub blocks, which doesn't really work either.
Anyone had any success with this flow?
could be in the form of background color or just a simple colored box around the url bar
I recently bought a water based stain that comes in a regular metal paint can. And it wood take me a long to time to finish it since I mostly build small things like knife handles and so on. I hate working with that metal can because every time I need to take a little for a coat, I have to have something to pry it open with, and doing that multiple times, the lid bents around the edges and gets stuck and when I pry it open it sometimes snags and spills and it’s just terrible because I do everything in my house and want to avoid spills at all costs. My question is if I can just pour that stain into a mason jar per say and keep it there without it drying out? Is it safe to do that?
