@fruitcantfly@programming.dev

comments

• The problem of enums in other languages is that they do not make for a distinct type. They are just integers in a name. Or at least that is the case for C and Java enums. Python and JavaScript do not even have enums, which is even worse.

  Strongly typed enums is hardly unique to Rust.

  C++ has had them for a long time, for example: Using a plain integer type where an enum is expected has been prohibited since at least C++98. You can still use an enum in the place of an int, unless you use scoped enums (C++11 or later), which also require an explicit cast to convert from enum to the underlying type.

  And Python has had some form of enum since since 3.4: docs.python.org/3/library/enum.html. It’s not a language level feature, but that probably wouldn’t make much of a difference, and it’s as type safe as anything else in the language. But you will get a error when using type-hints, if you pass the wrong type to a function expecting an enum:

  from enum import Enum
  
  class MyEnum(Enum):
      A = 1
      B = 2
  
  def foo(_: MyEnum): ...
  
  foo(1)  # error: Argument 1 to "foo" has incompatible type "int"; expected "MyEnum"  [arg-type]
  

  on Made this after someone noticed her face looked like PirateSoftware in c/programmer_humor@programming.dev · 10 Sep 2026

• But if you actually described this methodology in your PR, then it’d no doubt be closed immediately, based on the spirit of the rules rather than the exact letter of the rules.

  Rules like these ultimately presuppose that the contributor is acting in good faith. Because otherwise the contributor could just lie about using an LLM. They don’t need to engage in rules-lawyering or jump through hoops to circumvent the rules

  on The Rust programming language project is adopting an LLM policy in c/technology@lemmy.world · 14 Aug 2026