They’re semantically different for PATCH requests. The first does nothing, the second should unset the name field.

Then, you could take those comments, and have the compiler use them to ensure you’re using the right variable in the right place. Oh wait, we just invented a type system.

Works even better in Ruby, as the code as given is valid, you just need to monkey patch length:

#!/usr/bin/env ruby

module DayLength
  def length
    if ["Sunday", "Monday", "Tuesday", "Wednesday", "Thursday", "Friday", "Saturday"].include? self
      "24 hours"
    else
      super
    end
  end
end

class String
  prepend DayLength
end

day = "Monday"

x = day.length

print(x)

It could be Ruby; puts is more common, but there is a print. With some silly context, the answer could even be correct:

#!/usr/bin/env ruby

module DayLength
  def length
    if ["Sunday", "Monday", "Tuesday", "Wednesday", "Thursday", "Friday", "Saturday"].include? self
      "24 hours"
    else
      super
    end
  end
end

class String
  prepend DayLength
end

day = "Monday"

x = day.length

print(x)

I’m sorry to hear that. I think at one point in my past, about half my job was tracking down nil dereference errors in Ruby. And probably a quarter was writing tests for things a good type system would catch at compile time.

I’m waiting for Outlook (Taylor’s Version).

What? The people who made him buy it got paid already. I’m sure they’re laughing every time they see it drop in value.

Python with numpy/matplotlib/scipy.

Isn’t that what Unreal Engine has?

I’ve also heard it referred to as “source available”.

deleted by creator

I also appreciate that you’re supposed to learn Django 19 years before you learn Python.

I guess I’m neutral evil? I call shenanigans.

I think modern inverter units are not less efficient when oversized. They are able to run at varying levels rather than cycling.

I personally don’t think they do, but an argument can certainly be made. Rust proc macros can run arbitrary code at compile time. Build scripts can also do this.

This means, adding a dependency in Cargo.toml is often enough for that dependency to run arbitrary code (as rust-analyzer will likely immediately compile it).

In practice, I don’t think this is much worse than a dependency being able to run arbitrary code at runtime, but some people clearly do.