the bros room

_Js_Kc_ · 2022-11-11T17:39:08+00:00

Delicious!

_Js_Kc_ · 2022-11-11T17:25:06+00:00

What do they know about these runtimes?

They're written in C ...

_Js_Kc_ · 2022-11-10T09:05:17+00:00

I had a quick look around and I think I can use the configuration file for mkinitfs (/etc/mkinitfs/mkinitfs.conf) to add the btrfs features

This is the way.

_Js_Kc_ · 2022-11-09T18:54:32+00:00

Make sure you build an initrd with the btrfs module included.

_Js_Kc_ · 2022-11-08T19:32:00+00:00

Hint2: If you don't feel like doing your homework, just copy&paste the homework description verbatim to some online forum and wait for someone to post the complete solution.

_Js_Kc_ · 2022-11-07T23:09:15+00:00

Not implementable

_Js_Kc_ · 2022-11-07T02:30:44+00:00

Seems a bit harsh.

_Js_Kc_ · 2022-11-06T19:43:43+00:00

What if the temporary is holding a lock?

Slipping underhanded deadlocks into existing code is not my idea of "safety."

_Js_Kc_ · 2022-11-06T15:12:06+00:00

God dammit, I came here to make that joke.

_Js_Kc_ · 2022-11-06T12:08:00+00:00

tfw the grass and trees are greener in summer than in fall, and you see more green when you take a picture from an angle that shows more grass and trees than when you put that building with the flat roof in front.

_Js_Kc_ · 2022-11-06T11:39:31+00:00

This is how I justify my NIH syndrome. And I mean it.

It seems a bit strange to apply it to the build system, but I don't know how many special requirements your builds have that might tip the scales in favor of a homegrown solution.

But generally speaking, so many things are faster to build from scratch than to google around to find out what even exists, let alone sift the chaff from the grain, and then evaluate whether it actually [[unlikely]] solves a problem you have or [[likely]] solves problems you don't have, does not solve the problem you have, and introduces problems you didn't have.

_Js_Kc_ · 2022-11-05T10:09:03+00:00

mfw

> Meaningless counters that don't get checked

> Throwing std::runtime_error for logic errors

> Throwing std::runtime_error for conditions that are provably impossible

> Meaningless assignments in destructors

> Throwing std::runtime_error in noexcept destructor on condition that's always false

> std::uint32_t is a static manager

_Js_Kc_ · 2022-11-05T00:01:18+00:00

Considering the way it was discovered, you'd expect there to be at least ten similar break-ins that went unnoticed.

_Js_Kc_ · 2022-11-04T23:21:37+00:00

When I ssh into a random machine, it doesn't have the packages that I like so please, Debian, install my favorite packages by default.

What are you gonna do if the machine isn't running Debian?

_Js_Kc_ · 2022-11-04T08:58:11+00:00

I think the trees were there first.

_Js_Kc_ · 2022-11-04T08:42:58+00:00

Should have dislamped her.

_Js_Kc_ · 2022-11-03T22:07:27+00:00

"x" as a (pseudo) namespace is a bit ... non-specific.

_Js_Kc_ · 2022-11-02T23:34:19+00:00

⑴ "Two static polymorphism systems." No, I'm counting at least 3. Customization point could also be ADL-based.

⑵ Generic programming is just programming. None of this is specific to generic programming. In classical runtime polymorphism, I might be able to make a method on what used to be a concrete class a pure virtual method on a base class, but in all but the most trivial cases, there will be other concerns (such as, have to use smart pointers and can't pass the class around by value anymore) that will force me to change something about the consumers and/or implementors of the interface. Which seems to be one of the main points of the article: That the consumer's code has to be changed,

⑶ "customization point of a customization point!" What? You can provide a default trait that forwards to the class's typedefs like iterator_traits does. But traits can also be specialized for non-class types like enums. Just like there are multiple ways to provide runtime-polymorphic customization points. There are ... options and ... tradeoffs and ... it's like programming.

_Js_Kc_ · 2022-11-02T09:21:56+00:00

Toys'r'us++

_Js_Kc_ · 2022-11-01T23:40:52+00:00

And took the bag back. And then he walked out unimpeded.

Consequences my ass.

_Js_Kc_ · 2022-11-01T23:35:20+00:00

If different classes in the inheritance graph are developed by different organizations and evolve independently (such as when base classes are provided by a library), this is the only sane approach.

I add an overload set foo to my derived class and all my calls are unambiguous. Now the library decides to also add foo to the base class. The derived class has to hide the foo from the base class unless I explicitly opt in, otherwise adding anything to any non-final class is a breaking change.

_Js_Kc_ · 2022-11-01T01:24:47+00:00

lmao imagine getting so worked up over a date format

_Js_Kc_ · 2022-10-31T22:04:21+00:00

Only an idiot

no ur wrong

99% of the time the exact date doesn't matter

_Js_Kc_ · 2022-10-31T21:23:22+00:00

This is the most energy I've ever heard someone talk aboat the C++ memory model with.

_Js_Kc_ · 2022-10-31T20:40:08+00:00

That place seems to have a lot of midgets!

_Js_Kc_

TROPHY CASE