There are some design features in programming languages that make code written in the language difficult to debug (e.g. C's default fallthrough behavior).

So it would be helpful to make a list of these design errors, so that language designers can avoid it while designing a language.

  • 2
    $\begingroup$ This question is just too broad currently to work well in the model of the site. If you can narrow it down to a more concrete question then you can edit and reopen it. For example, at the least it'd be necessary to have a firm concept of what hard-to-debug meant in order to evaluate answers. "What are some ..." is generally not a productive format either, so it would be good to narrow that down too. Have a look at the help center for more on the sorts of questions that work well here. $\endgroup$
    – Michael Homer
    Aug 30, 2023 at 6:49
  • 2
    $\begingroup$ I agree that as it stands is too broad for the SE format but I also think it is useful line of questioning (not necessarily a single question) if we can phrase it better. So I've asked on meta - langdev.meta.stackexchange.com/questions/599/… As it stands it might be better to ask on r/programminglangages $\endgroup$ Aug 30, 2023 at 11:17
  • $\begingroup$ The fallthrough thing in C is a good thing - it keeps the user from repeating the same code over and over for different cases. Of course, regex switches (see vovkos.github.io/jancy/language/regex_switches.html ) would fix that. $\endgroup$ Sep 5, 2023 at 21:30


Browse other questions tagged .