61
Is it really a breaking change if a method changes output after an update? (lemmy.world)
submitted 2 years ago by to c/programming@programming.dev
23 comments fedilink hide all child comments
 

This might seem obviously "yes" at first, but consider a method like foo.debugRepr() which outputs the string FOO and has documentation which says it is meant only to be used for logging / debugging. Then you make a new release of your library and want to update the debug representation to be **FOO**.

Based on the semantics of debugRepr() I would argue that this is NOT a breaking change even though it is returning a different value, because it should only affect logging. However, if someone relies on this and uses it the wrong way, it will break their code.

What do you think? Is this a breaking change or not?

you are viewing a single comment's thread
view the rest of the comments
[–] 7 points 2 years ago

It's your project, do whatever you want.

If changing any observable behavior meant a breaking change, then you couldn't ever change anything. Even a bug fix changes observable behavior. Some people don't seem to be considering that here...

  • permalink
  • fedilink
  • source
    •