scottyjoe9

Yep this is me. I love learning languages and I'm a software dev for my job.

Honestly, I don't like this either. It's definitely unfortunate.

I can see how you could think of the setter like Current?.Response.set_ContentType("text/json") and then if Current is null you just skip the assignment like you would any other method call.

You are correct, sorry. I've edited my post.

Nevermind, see my edit - I was wrong.

Shit, bad choice of third instance... Who hasn't beehaw defederated?

It's not currently possible because the null conditional operator returns a value not a variable. Looks like there was some discussion on stack overflow and a GitHub issue was created a while ago but it hasn't had much activity recently.

~~Yes, comments from users on instances A and B on a post on C are visible to users on all three instances. De/federation is a way for admins of a specific instance to control which users can interact with posts on their instance. Eg: beehaw defeds sh.itjust.works so users from sh.itjust.works cannot interact with posts on beehaw. Users from both instances can interact with each other on posts on lemmy.world though.~~

~~Edit: In reality, beehaw has defederated both sh.itjust.works and lemmy.world. In my theoretical example, only sh.itjust.works has been defederated.~~

EDIT: I actually tested it and I'm wrong! I logged into my beehaw alt account and came to this thread but I can't see this comment as it's from sh.itjust.works. Because my comment is hidden, I also couldn't see the thread attached to this comment section so the comment thread looked empty.

Sorry for confusion.

I don't agree with this one. The meaning of words change and that's true of 'Less'.

I generally don't agree with these prescriptivist positions though.

Almost

When a GitHub issue is closed as complete it means someone has fixed the bug in the source code (or the developers have decided it's not a bug). It doesn't necessarily mean the fix has been shipped in a new version or that the server you're connecting through has been updated to a version with the fix. In this case, they haven't shipped a new version with this fix in it. I'm not sure what the delivery cadence will be but I assume a new version will go out in the next week or so and then once your server admin upgrades their server the problem will be fixed for you.

This is a known issue on the web ui - we're looking into it.