this post was submitted on 31 Aug 2025
29 points (100.0% liked)

Programming

24135 readers
384 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 2 years ago
MODERATORS
snowe@programming.dev
Ategon@programming.dev
MaungaHikoi@lemmy.nz
UlrikHD@programming.dev
29
The Koka programming language (lwn.net)
submitted 4 months ago by cm0002@lemmy.world to c/programming@programming.dev
11 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] atzanteol@sh.itjust.works 3 points 4 months ago

With OOP languages, class methods can create a dichotomy of expected returns: Using a list reversal as an example, will a list.reverse(some_list) function reverse the list in-place, or return a copy of the reversed list and leave the original in-tact?

Mmm - that is an excellent example, though not one specific to OOP... But I see your point. I think Kotlin and other languages have addressed these types of issues with 'mutability' as part of the type where it becomes explicit which variables can be modified. Kotlin even has "MutableList" as distinct from "List" which lets you say whether a list's contents can be modified.