OddObserver posted:

I can appreciate the buttons compared to trying to deal with keyboard events (which historically belonged in this thread).

Tann posted:

Just found you can do something like sql injection in my game lol

I let you rename heroes between fights and it all uses my weird modding thing. If you rename them to eg "jenny.hp.500" then they gain the name "jenny" and 500hp.

ultrafilter posted:

https://twitter.com/thatfrood/status/1711479173049385282

Ihmemies posted:

Mind_Taker posted:

code:

public dynamic function(dynamic data) {
    int id = (int)(data.id);

....

    return some_string;
}

Stuff like this is everywhere in the codebase I'm reviewing for the job I just started.

Mind_Taker posted:

code:

public dynamic function(dynamic data) {
    int id = (int)(data.id);

....

    return some_string;
}

Stuff like this is everywhere in the codebase I'm reviewing for the job I just started.

Mind_Taker posted:

code:

public dynamic function(dynamic data) {
    int id = (int)(data.id);

....

    return some_string;
}

Stuff like this is everywhere in the codebase I'm reviewing for the job I just started.

raminasi posted:

Is it doing some weird interop thing?

more falafel please posted:

I'm glad that in the modern C++ codebases I've had exposure to, auto and decltype are only really ever used either idiomatically (no need to specify what the type of container.begin() is) or to simplify when you're already specifying the type one or more times in the declaration.

Surprise T Rex posted:

Death to the ViewBag.

Rottbott posted:

Auto is never as bad as this anyway, because the variable still has a type, and your IDE can tell you what it is.

Presto posted:

My use of 'auto' has shrunk to three cases.

1. Declaring iterators, especially for complex types, because the type names get really long and I'm far too lazy to type that crap.

2. Declaring variables that are initialized with the result of a cast, because the type is obvious because it's right there in the cast.

3. Structured bindings, because they are sexy and I love them.

The rest of the time I'd rather see the actual type.

more falafel please posted:

It can still bite you in the rear end if you change, say, the return type of a function that's initializing an auto. Harder to do, but still doable.

Presto posted:

My use of 'auto' has shrunk to three cases.

1. Declaring iterators, especially for complex types, because the type names get really long and I'm far too lazy to type that crap.

2. Declaring variables that are initialized with the result of a cast, because the type is obvious because it's right there in the cast.

3. Structured bindings, because they are sexy and I love them.

The rest of the time I'd rather see the actual type.

Zopotantor posted:

code:

auto fart = Fart(42);

Foxfire_ posted:

I think there's a better argument that every one argument constructor should be marked explicit and not be participating in implicit conversions unless you're absolutely sure you want that

Ranzear posted:

There's supposed to be a 'private' account setting. This ignores it.

quote:

Can I set my profile to be private?

Currently, there are no private profiles on Bluesky.

Dylan16807 posted:

Where did you hear that?

https://blueskyweb.xyz/blog/5-19-2023-user-faq

That page also says blocks are public, though I suppose not every user might know that.

Mutes are private.

Dylan16807 posted:

Where did you hear that?

RPATDO_LAMD posted:

It looks pretty stupid for 1-argument constructors like that where you can just use "Fart fart = 42" but it can be nice to cut down repetition for multi-arg constructors where you actually do have to type out the constructor name

for example if I want to make a vector with 10 pre-initialized objects:

C++ code:

std::vector<MyAnnoyinglyLongCustomTemplateClass<Foo>> foos = std::vector<MyAnnoyinglyLongCustomTemplateClass<Foo>>(MyAnnoyinglyLongCustomTemplateClass<Foo>(someDefaultValue), 10);
// versus this which sucks a little bit less:
auto foos = std::vector<MyAnnoyinglyLongCustomTemplateClass<Foo>>(MyAnnoyinglyLongCustomTemplateClass<Foo>(someDefaultValue), 10);

RPATDO_LAMD posted:

It looks pretty stupid for 1-argument constructors like that where you can just use "Fart fart = 42" but it can be nice to cut down repetition for multi-arg constructors where you actually do have to type out the constructor name

for example if I want to make a vector with 10 pre-initialized objects:

C++ code:

std::vector<MyAnnoyinglyLongCustomTemplateClass<Foo>> foos = std::vector<MyAnnoyinglyLongCustomTemplateClass<Foo>>(MyAnnoyinglyLongCustomTemplateClass<Foo>(someDefaultValue), 10);
// versus this which sucks a little bit less:
auto foos = std::vector<MyAnnoyinglyLongCustomTemplateClass<Foo>>(MyAnnoyinglyLongCustomTemplateClass<Foo>(someDefaultValue), 10);

Ranzear posted:

Extrapolated from elsewhere, unfortunately. Silly me and my expectations.

I could have just gestured at bluesky in general, lack of DMs, post tagging of any form (topical nor content warning beyond three things), video or even loving animated GIF support even after four years, but likes and blocks being public is just way too much stalking and harassment potential to even dip a toe into now.